I'll offer some thoughts. I'm seeing upsertV() as an idempotent getOrCreate
call which always returns a vertex with the label/property values specified
within the step. It's sort of a declarative pattern: "return this vertex to
me, find it if you can, create it if you must."
On that account, I do
ah - regarding 2, ok i couldn't remember and i didn't notice where we
talked about that when I scanned the thread. I've updated the gist
accordingly:
https://gist.github.com/spmallette/5cd448f38d5dae832c67d890b576df31
On Tue, Dec 8, 2020 at 10:51 AM David Bechberger
wrote:
> For #1 and 3 I
For #1 and 3 I agree. For #2 I thought that we agreed that the properties
within the upsert were going to be for creation only and that any
properties that needed to be updated would be done via the standard
property() syntax after the upsert. e.g.
g.upsertV('person', [name: 'marko'],
I started a expanded this discussion to gremlin-users for a wider audience
and the thread is starting to grow:
https://groups.google.com/g/gremlin-users/c/QBmiOUkA0iI/m/pj5Ukiq6AAAJ
I guess we'll need to summarize that discussion back here now
I did have some more thoughts to hang out there
Mark Richman created TINKERPOP-2488:
---
Summary: Using ws:// when Neptune requires wss:// doesn't throw
exception
Key: TINKERPOP-2488
URL: https://issues.apache.org/jira/browse/TINKERPOP-2488
Project:
Guo Junshi created TINKERPOP-2487:
-
Summary: Add steps to support basic analysis like standard
deviation and percentile
Key: TINKERPOP-2487
URL: https://issues.apache.org/jira/browse/TINKERPOP-2487
Pr
