Anonymous
My feedback
-
86 votes
Work for this feature has been started. Will update here when this feature becomes generally available.
Thank you.
Anonymous
supported this idea
·
-
47 votes
Work for this feature has been started. Will update here when this feature becomes generally available.
Thank you.
Anonymous
supported this idea
·
An error occurred while saving the comment -
37 votes
We’ve evaluated this request and at this time we are deferring this from our road map. Will leave this as open so we can consider this in the future.
Thanks.
An error occurred while saving the comment Anonymous
commented
In the current stage:
http://tinkerpop.apache.org/docs/current/reference/#vertex-properties
.property(list, 'name', 'm. a. rodriguez')
is working for vertices. Arrays in Edges are not working.Cosmos DB tries to focus everything on SQL Query Language. If you have Arrays in properties, you might come into trouble. In future Cosmos Db Versions (so if you create a new one in Azure) , arrays wont be supported. Therefore, the opportunity to connect the DB with Elasticsearch or Azure Search will become possible. This can only happen if you can write plain SQL.
If you need an array for now, you have to build Edges with those values. Sure this might be a big overhead for you.
If you need it so badly, you might go to Janusgraph, neo4j or Titan with native support for that. Janusgraph also has Arrays in Edges (properties). Good Luck ;)
-
888 votes
Update on this item.
Bytecode implementation is now targeting the first half of 2020 to provide stability and performance improvements in the platform.
Apologies for the delay. We are continuing to work on this. Will announce here when this becomes available.
Thanks.
An error occurred while saving the comment Anonymous
commented
Nice! Is there any release date for a preview?
Anonymous
supported this idea
·
Some updates on this? It is not possible to use it, if the cost goes up exponentially.
Sorry to say..