You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Stephen Mallette (Jira)" <ji...@apache.org> on 2020/10/19 15:14:00 UTC
[jira] [Closed] (TINKERPOP-2442) Make Translators that work in Java
part of gremlin-core
[ https://issues.apache.org/jira/browse/TINKERPOP-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephen Mallette closed TINKERPOP-2442.
---------------------------------------
Fix Version/s: 3.4.9
3.5.0
Resolution: Done
> Make Translators that work in Java part of gremlin-core
> -------------------------------------------------------
>
> Key: TINKERPOP-2442
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2442
> Project: TinkerPop
> Issue Type: Improvement
> Components: process
> Affects Versions: 3.4.8
> Reporter: Stephen Mallette
> Assignee: Stephen Mallette
> Priority: Major
> Labels: deprecation
> Fix For: 3.5.0, 3.4.9
>
>
> {{Translator}} instances have lived with their GLV implementations for the language they represented. This led to us deprecating the {{PythonTranslator}} which lived with gremlin-python as Jython support was being deprecated out. The {{Translator}} functionality is helpful though and it's a shame to lose it as a lot of times we give an answer in Groovy and translating to Python takes some manual effort. If we organize translators differently so that each language gets translators to other languages then we give users the functionality they need to more seamless move from one GLV to the next.
> For this change we will move the deprecated {{PythonTranslator}} and the {{GroovyTranslator}} to gremlin-core as that module is the one for "Gremlin in Java". {{GroovyTranslator}} will be deprecated from gremlin-groovy.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)