Just a quick update. Work on this feature continues but is taking longer than expected.
We have recently published guidance how how users who can run Windows in a VM whether on Parallels or Virtual Box with a Mac or Linux host can use the Cosmos emulator. Please feel free to use this as a workaround.
When this feature is complete we will update here.
Thank you.Gutemberg Ribeiro commented
Awesome that the work is in progress. Will it be OSS'd? Any probably ETA? Thanks!
Work on Bytecode support has started. Will update here when this becomes generally available.
Thank you for your suggestion and votes.Gutemberg Ribeiro commented
With the recent announcement of CosmosDB which includes Gremlin APIs, is there any plan to have a more fluent/linq/lambda-friendly APIs on .Net SDK?
I'm looking at this sample https://github.com/Azure-Samples/azure-cosmos-db-graph-dotnet-getting-started/tree/master/GraphGetStarted from docs, and the Gremlin queries are fully string-based.
I could contribute that to a package like Microsoft.Azure.Graphs.Extensions or something like that.
I know that lambda/linq syntax don't map 100% to the the Gremlin one.
So the idea would be translate:
g.addV('person').property('id', 'thomas').property('firstName', 'Thomas').property('age', 44)"
to something like that:
graph.Vertice<Person>().Property(p => p.Id == "thomas").Property(p => p.FirstName == "thomas").Property(p => p.Age == 44);
That would internally build the proper Gremlin query string and send to CosmosDB.
What do you guys think?
(The original issue on GH https://github.com/Azure/azure-documentdb-dotnet/issues/257)
269 votesGutemberg Ribeiro shared this idea ·