[
https://issues.apache.org/jira/browse/TINKERPOP-3165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17956646#comment-17956646
]
Lyndon Bauto commented on TINKERPOP-3165:
-----------------------------------------
[~spmallette] Hmmm. So this issue arose in our OLAP implementation because we
bootstrap Gremlin Server in our spark master node, allowing it to run OLTP and
OLAP queries. OLTP queries can be somewhat useful as your are testing things
and messing around, however the main use case is OLAP so maybe binding that to
'g' makes sense. We ultimately want the String query support because some
people may want to run queries from gdotv.
The one thing that makes me hesitate to just bind "g" to directly hit OLAP is
that I can see being able to hit the regular OLTP engine to use call steps and
such as somewhat useful (perhaps you want to manage your secondary indexes etc)
and right now call steps do not work in OLAP (at least for us, since they are
not serializable etc).
Perhaps that's something we can fix on our side anyway.
I guess the workaround would then be bind "g" to OLAP and "gOLTP" or whatever
to OLTP.
> `withComputer()` is not defined in grammar
> ------------------------------------------
>
> Key: TINKERPOP-3165
> URL: https://issues.apache.org/jira/browse/TINKERPOP-3165
> Project: TinkerPop
> Issue Type: Bug
> Components: process
> Affects Versions: 3.7.3
> Reporter: Valentyn Kahamlyk
> Priority: Major
>
>
> it is impossible to use olap with string requests because `withComputer` is
> not supported
> {code:java}
> final Client.ClusteredClient client =
> Cluster.build(<IP>).port(8182).create().connect();
> final ResultSet result = client.submit(
> "g.withComputer().V().hasLabel(\"Person\").count().next()",
> "g");
> System.out.println("Result: " + result.one());
> {code}
> result error
> {code:java}
> Failed to interpret Gremlin query: Query parsing failed at line 1, character
> position at 2, error message : no viable alternative at input
> 'g.withComputer'{code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
