Skip to main content

Release Notes 0.17.11

This document describes what has changed in Macrometa release 0.17.11. To check what version of GDN you are using, use the RestVersionHandler API command.

New Features​

The following new features are included in this release.

Search and Stream Workers are in GA​

Search and Stream Workers, previously only available in closed beta, are now generally available for everyone to use.

Invite User​

You can now invite users to your Macrometa account by sending them email.

Invite Users was added as a result of this feature.

Manage Attributes in Console​

You can now manage attributes for users and API keys in the Macrometa console.

Attributes was added as a result of this feature.

Akamai EdgeWorker Support - Preview​

This release adds support for Akamai edge workers as functions in GDN. For more information, refer to Akamai EdgeWorkers.

SQL Support - Beta​

Macrometa now supports SQL queries. Support will be expanded in future releases.

SQL in Macrometa was added as a result of this feature.

Redis Support - Beta​

Macrometa now offers Redis support.

Redis Mode Collections and Redis in Macrometa were added as a result of this feature.

Kafka Support - Beta​

This release adds support for some Kafka clients in the GDN. For a list of supported clients, refer to Kafka on GDN.

Feature Updates​

The following features updates are included in this release.

Migration to Play - Breaking Change​

The previous generic global URL api-play.paas.macrometa.io is no longer valid.

Customers with Macrometa Play tier accounts can use api-play.paas.macrometa.io as a substitute, but we do not recommend it.

Instead, we recommend that you use an account-specific global or regional URL, which you can find in the API Reference in the Macrometa web console or on your GeoFabrics page. Any endpoint listed on the GeoFabric will accept API calls if you prepend api- to it.

For more information, refer to Unique Global URL vs. Generic.

Stream Worker Prefixes​

You can now prepend a stream worker name to the aggregation tables that it creates. For example, if the stream worker name is SampleAggregationApp and the aggregation is TradeAggregation, then it will create tables like SampleAggregationApp-TradeAggregation_SECONDS. Previously, it was just TradeAggregation_SECONDS.

Auth Improvements​

  • We redesigned Macrometa authorization to make our service more efficient and stable.
  • The account signup and login screens have been updated and improved.

API Updates​

This release includes the following API changes.

Issue #Description
APIDOC-51Added stream worker parameters maxLogsLengthKBPerMinutePerWorker and maxCpuSecondsPerMinutePerWorker.
APIDOC-54In API reference docs, corrected a typo in insertDocument description.
DB-1692The fabric creation endpoint in the API now allows up to 40 characters for fabric names, just like in the web console.
DB-1704Clarified in the API documentation for Import API that the _key must be a string.

Import and Export Changes (DB-1660)​

  • You can now export in Vpack format.
  • Added batching support for importing and exporting.

User Changes (DB-1783)​

  • The user parameter is deprecated and will not be used while creating the new user. For backward compatibility, it will not generate any errors.
  • Provided a new optional parameter displayName to set the display name of the user. Whitespaces are allowed.

Here is a sample for the updated request body:

curl -X 'POST' \ 'https://api-qa6.eng.macrometa.io/_api/user' \ 
-H 'accept: application/json' \ 
-H 'Content-Type: application/json' \ 
-H 'Authorization: bearer <token> \
-d { 
    "active": true, 
    "email": "test1@bar1.com", 
    "passwd": "P@55w0rd", 
    "displayName":"John Doe" 
    }'

Known Issues​

The following known issues were introduced in this release.

Local stream is not accessible after upgrade from 17.10 to 17.11​

Problem: Sometimes global streams are not accessible in the Macrometa console.

Workaround: If you encounter this error, then run the Publish Message API endpoint for particular stream to get rid of the issue.

POST /_fabric/_system/_api/streams/{stream}/publish

For more information about running API commands, refer to APIs.

Defect Fixes​

The following defects were fixed in this release.

Defect #Description
DB-1625Cursor API not working as expected with stream:true option in payload.
DB-1637In the C8QL query, if the filters are applied on the non-indexed keys, the query is likely to time out.
DB-1666The item count on the screen is not updating when an item is inserted or deleted from a Dynamo collection.
DB-1667Dynamo scans with filter expressions are not working as expected.
DB-1668Improved error text in duplicate node error for graphs to be more user-friendly.
DB-1714MaxDocumentSize limit error message in Dynamo is incorrect.
DB-1801API /_api/key/validate returns HTTP code 200 with message 'non-representable type' when no request body is sent.
DB-1831Graph with a vertex collection not loading normally. It only loads when you click on Full Graph option.
DB-1855Maximum stored query workers limit is not applied across all regions.
GUI-236Newly-created key-value collection does not replicate in other geo locations.
GUI-239Could not update existing users in an account.
GUI-241Search functionality does not work on Accounts page.
GUI-249KV Pair Edit form does not show the date and time values correctly.
GUI-395New index for a collection does not appear in the UI.
GUI-525Import Documents button is improperly aligned.
GUI-536When a non-root user opens the permission configuration tab for an API key, the Read-only option is in a disabled state. The same option is enabled for collections.
GUI-666The user is redirected to the login page after they change the fabric.
GUI-834UI breaks when a non-root user with access to a custom fabric and no access to the system fabric logs in.
GUI-859Garbled error message appears on the login page when a non-root user with no access to fabrics logs in after changing their password.
GUI-864Query editor bind parameter saves JSON Object as [object Object].
GUI-868Non-root users are unable to create a new API key in the Macrometa console.
GUI-903Wrong error message in tooltip for import collection scenario.
GUI-1282Validation for field name is missing while adding mapping definition.
GUI-1298Alignment issues on Query Worker page.
GUI-1315Query gets stuck when you press the Run Query button quickly multiple times.
GUI-1441Support link is cropped when viewing the console on a screen with 1536 x 864 resolution.
GUI-1513Bind parameter key does not update when run by pressing Run Query.
GUI-1517No message is shown when the user successfully purges a Dynamo Table collection.
GUI-1520JSON object attributes in a Dynamo Table collection are not visible in the web console.
GUI-1521Pagination is not working properly for Dynamo collections with JSON attributes.
GUI-1526Enabled and disabled region endpoints are not always displayed correctly in the web console.
GUI-1537Typo in stream creation success message.
GUI-1547Download CSV button is missing in some cases.
GUI-1554Graph view in Query Results in the Query Workers page is not stable.
GUI-1555Typo in Primary Sort tool tip in Create New View modal.
GUI-1571Creating two fabrics with access to different regions shows all three regions available to both fabrics.
GUI-1573A non-root user that has access permission for fabric and read/write for collections cannot create or delete documents in the web console.
GUI-1574Multi-edge graph is not working.
GUI-1575An error in one graph prevents other graphs from loading.
GUI-1577Edit user password message does not specify required special characters.
GUI-1582Non-root users with read-only access to a fabric and read-write access to collections are not able to create and save query workers in the web console.
GUI-1583Non-root users with read-only access to a fabric and read-write access to collections are not able to modify data in collections via the web console.
GUI-1606Text wrapping is not working properly in the API header descriptions in the API Reference in the web console.
STRM-418Stream limits are not properly applied on custom fabrics.
STRM-443Stream deletion is not always replicated in other regions.