Hi,
However, in general we just need an “object mapper pattern.” For instance:
For any JSON object { } that has a @type field, the @type value maps to a
deserializer. Thus, while we need to be able to serialize/deserialize the
standard Vertex/Edge/VertexProperty/etc. the representation should
[
https://issues.apache.org/jira/browse/TINKERPOP-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Plurad updated TINKERPOP-1379:
Description:
Jason Plurad created TINKERPOP-1379:
---
Summary: unaccounted excess in TailGlobalStep
Key: TINKERPOP-1379
URL: https://issues.apache.org/jira/browse/TINKERPOP-1379
Project: TinkerPop
Issue
$ bin/validate-distribution.sh 3.2.1
Validating binary distributions
* downloading Apache Gremlin Console
(apache-gremlin-console-3.2.1-bin.zip)... OK
* validating signatures and checksums ...
* PGP signature ... OK
* MD5 checksum ... OK
* SHA1 checksum ... OK
* unzipping Apache Gremlin
ah - sorry - didn't follow that. that makes sense to me. inVLabel and
outVLabel are kinda awkward. +1 from me on that one.
On Tue, Jul 19, 2016 at 3:23 PM, Robert Dale wrote:
> On Tue, Jul 19, 2016 at 3:13 PM, Stephen Mallette
> wrote:
> >>
> >> > -
On Tue, Jul 19, 2016 at 3:13 PM, Stephen Mallette wrote:
>>
>> > - VertexProperty and (edge) Property are implicit types. I don't know
>> > if this is ok. Could they ever be used outside of their parents where
>> > they would need to be typed?
>>
>> I agree with the
Ran all the driver tests again neo4j and tinkerpop and everything works as
expected.
VOTE: +1
On Tue, Jul 19, 2016 at 9:20 AM, Stephen Mallette
wrote:
> Hello,
>
> We are happy to announce that TinkerPop 3.2.1 is ready for release - note
> the lack of "-incubating"
>
> > - VertexProperty and (edge) Property are implicit types. I don't know
> > if this is ok. Could they ever be used outside of their parents where
> > they would need to be typed?
>
> I agree with the VertexProperty remark. That's one last question I wanted
> to solve, if we go for typing
pieter martin created TINKERPOP-1378:
Summary: Provide a config for Optout
Key: TINKERPOP-1378
URL: https://issues.apache.org/jira/browse/TINKERPOP-1378
Project: TinkerPop
Issue Type:
There's also Path that can be returned from a query. It looks like
GraphSON 1.0 handles this today in the REST API but it's not typed as
a path.
On Tue, Jul 19, 2016 at 2:14 PM, gallardo.kev...@gmail.com
wrote:
>
>
> On 2016-07-19 18:02 (+0100), Robert Dale
On 2016-07-19 18:02 (+0100), Robert Dale wrote:
> - It seems redundant to nest a vertex or edge inside a type-value
> object and is inconsistent with a VertexProperty.
> - VertexProperty and (edge) Property are implicit types. I don't know
> if this is ok. Could they ever be
On 2016-07-19 17:47 (+0100), Stephen Mallette wrote:
> it should - properties are a Map of Lists of Property values.
>
> On Tue, Jul 19, 2016 at 12:45 PM, Dylan Millikin
> wrote:
>
> > Quick question which is probably handled automatically but
- It seems redundant to nest a vertex or edge inside a type-value
object and is inconsistent with a VertexProperty.
- VertexProperty and (edge) Property are implicit types. I don't know
if this is ok. Could they ever be used outside of their parents where
they would need to be typed?
- Edges:
-
it should - properties are a Map of Lists of Property values.
On Tue, Jul 19, 2016 at 12:45 PM, Dylan Millikin
wrote:
> Quick question which is probably handled automatically but is this working
> with multiple cardinalities on properties?
>
> On Tue, Jul 19, 2016 at
Quick question which is probably handled automatically but is this working
with multiple cardinalities on properties?
On Tue, Jul 19, 2016 at 12:05 PM, gallardo.kev...@gmail.com <
gallardo.kev...@gmail.com> wrote:
>
>
> On 2016-07-15 16:25 (+0100), "gallardo.kev...@gmail.com"<
>
On 2016-07-15 16:25 (+0100),
"gallardo.kev...@gmail.com" wrote:
>
>
> On 2016-07-09 16:48 (+0100), Stephen Mallette wrote:
> > With all the work on GLVs and the recent work on GraphSON 2.0, I think it's
> > important that we have a solid,
That's typically how we do things here at TinkerPop - we tend to allow
"features that don't break public API" into the "z" of "x.y.z", however,
we're trying to wind down development on the 3.1.x line of code and not
introduce too much more there. I'd be open to a new bits of documentation
on that
Stephen, I noticed a couple of issues moved out of 3.1.4 for reason of
bug fixes only. Typically the semantic versioning is limited to
"public API". So I would argue that adding a service script (optional
usage at that) and a tutorial (documentation) would not affect the
public API or even general
[
https://issues.apache.org/jira/browse/TINKERPOP-980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette updated TINKERPOP-980:
---
Fix Version/s: (was: 3.1.4)
Release 3.1.4 is for bugs only at this point as
[
https://issues.apache.org/jira/browse/TINKERPOP-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette updated TINKERPOP-1342:
Fix Version/s: (was: 3.1.4)
3.2.2
Release 3.1.4 is for
[
https://issues.apache.org/jira/browse/TINKERPOP-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette updated TINKERPOP-1007:
Fix Version/s: (was: 3.1.4)
Release 3.1.4 is for bugs only at this point as
I've set up version 3.1.4 and 3.2.2 in JIRA and migrated all old issues in
those lines to them. As per previous discussion about the 3.1.x line, I'll
be moving out all issues that aren't bug or release related which should
just leave:
https://issues.apache.org/jira/browse/TINKERPOP-1376
Also, I
Hello,
We are happy to announce that TinkerPop 3.2.1 is ready for release - note
the lack of "-incubating" everywhere. :)
The release artifacts can be found at this location:
https://dist.apache.org/repos/dist/dev/tinkerpop/3.2.1/
The source distribution is provided by:
[
https://issues.apache.org/jira/browse/TINKERPOP-1358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette updated TINKERPOP-1358:
Fix Version/s: (was: 3.2.1)
> spark-gremlin tests require special setup
>
[
https://issues.apache.org/jira/browse/TINKERPOP-1358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette closed TINKERPOP-1358.
---
Resolution: Not A Problem
> spark-gremlin tests require special setup
>
[
https://issues.apache.org/jira/browse/TINKERPOP-1358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette closed TINKERPOP-1358.
---
Resolution: Not A Problem
> spark-gremlin tests require special setup
>
[
https://issues.apache.org/jira/browse/TINKERPOP-1358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette reopened TINKERPOP-1358:
-
> spark-gremlin tests require special setup
>
[
https://issues.apache.org/jira/browse/TINKERPOP-1358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette reopened TINKERPOP-1358:
-
> spark-gremlin tests require special setup
>
[
https://issues.apache.org/jira/browse/TINKERPOP-1358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette updated TINKERPOP-1358:
Labels: (was: spark)
> spark-gremlin tests require special setup
>
29 matches
Mail list logo