I vote "+1" for this feature.
On 2019/02/28 14:34:01, spmallette (GitHub) wrote:
> https://issues.apache.org/jira/browse/TINKERPOP-2171
>
> Allows `sparql()` step to be followed by Gremlin steps:
>
> ```text
> gremlin> g.sparql("SELECT * WHERE { }").out("knows").values("name")
> ==>vadas
> ==>
-1878/docs/src/reference/transpilers.asciidoc
>
> and provide a PR for that. Is that a good next step?
>
> On Wed, Feb 7, 2018 at 9:56 AM, Harsh Thakkar wrote:
>
> > Hi Stephen,
> >
> > Having more than one variables inside a GROUP BY or an ORDER BY clause is
> > a prob
ort and what our
> limitations are.
>
> Any thoughts on all that?
>
> > Dharmen and I did check your corrections and comments in the code. We
> found them appropriate.
>
> That's good to know. Thanks.
>
>
>
>
> On Tue, Feb 6, 2018 at 3:36
Factory.createModern()
> > > >> ==>tinkergraph[vertices:6 edges:6]
> > > >> gremlin> g = graph.traversal(SparqlTraversalSource.class).
> > > >> ..1> withStrategies(SparqlStrategy.instance())
> > > >> ==>
lease, i would
> > guess no earlier than February 2018 if all goes right with that. I also
> > don't mean to make it sound like sparql-gremlin needs to be part of that
> > release, so if it's not ready then, it's not ready and it releases with
> > 3.3.3. You&#x
e Semantic Web standards, SemWeb-like
> features -- such as schemas/ontologies and rules/reasoning -- keep finding
> their way in.
>
> How does your content-preserving RDF <--> PG interface compare with the
> GraphSail mapping, the PropertyGraphSail mapping(s), or with Hartig
> > > }â);
> > > }
> > >
> > > In this way, sparql is your SPARQLTraversalSource for each test and
> > query() will return a Traversal typed according (query() will have to have
> > solid generic support). From there, you would implement each and
each and every test that
> > is semantically possible with SPARQL (where SPARQ wonât be able to
> > semantically cover all Gremlin tests).
> >
> > Stephen has done a lot of recent work to generalize our test suite out of
> > Java so it is in a language agno
Hi Stephen and All,
Thanks for going through the code. I address your questions below (in the same
order):
1. Yes, this file can be removed. It was just to test the traversal method.
2. Yes, I have commented out the block of tests at this moment since we do not
need to run tests at mvn clean
APSHOT api
> > version?
> >
> > you should be on 3.3.1-SNAPSHOT for your API version now that you've
> > integrated sparql-gremlin into the tinkerpop code base. ultimately, it will
> > all release together as part of a single package, so it should all be on
> &
.3.1-SNAPSHOT for your API version now that you've
> integrated sparql-gremlin into the tinkerpop code base. ultimately, it will
> all release together as part of a single package, so it should all be on
> the same version.
>
> On Wed, Dec 13, 2017 at 6:43 AM, Harsh Thakkar wrote:
ng with appropriate configurations:
>
> http://tinkerpop.apache.org/docs/current/dev/developer/#documentation-environment
>
> Well, hope that gives you a few things to work on and think about for your
> first round of changes in your fork. Looking forward to seeing how this PR
> s
Hi Stephen,
Very well then, we will start the migration from today. Also we will submit the
signed iclas' today.
If we have some questions regarding building the code properly, can we feel
free to ask them here? I assume we might need some guidance on how to getting
things plugged in correctl
13 matches
Mail list logo
