[
https://issues.apache.org/jira/browse/TINKERPOP-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448584#comment-16448584
]
ASF GitHub Bot commented on TINKERPOP-1628:
-------------------------------------------
Github user spmallette commented on a diff in the pull request:
https://github.com/apache/tinkerpop/pull/844#discussion_r183484210
--- Diff: CHANGELOG.asciidoc ---
@@ -74,6 +74,7 @@ This release also includes changes from <<release-3-2-8,
3.2.8>>.
* TINKERPOP-1357 Centrality Recipes should mention pageRank and OLAP.
* TINKERPOP-1489 Provide a Javascript Gremlin Language Variant
* TINKERPOP-1586 SubgraphStrategy in OLAP
+* TINKERPOP-1628 Implement TraversalSelectStep.
--- End diff --
i know i pretty much always have false alarms about your changelog entries,
but this one looks amiss. we generate this portion of the changelog on release
so they shouldn't be edited. you just need an entry on 3.3.3 like we normally
have.
> Implement TraversalSelectStep
> -----------------------------
>
> Key: TINKERPOP-1628
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1628
> Project: TinkerPop
> Issue Type: Improvement
> Components: process
> Affects Versions: 3.3.0
> Reporter: Daniel Kuppitz
> Assignee: Daniel Kuppitz
> Priority: Major
>
> It should be possible to have nested {{select()}} or rather to select dynamic
> keys.
> {noformat}
> gremlin> aliases = ["marko":"okram"]
> gremlin> g.withSideEffect("a", aliases).V().hasLabel("person").
> values("name").as("n").
> optional(select("a").select(select("n")))
> ==>okram
> ==>vadas
> ==>josh
> ==>peter
> {noformat}
> I know there are more steps that could / should allow traversals, but to me
> {{select()}} seems to be the most important one (perhaps because the
> workaround is / can be super expensive).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
