Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Done
-
3.6.6
-
None
Description
Translator infrastructure uses bytecode and reflection which has a number of technical imperfections and exemptions for it to work properly. Switching to the grammar for translation simplifies the code, removes friction and complexity when generating GLV tests, and should perform better. The focus for this issue is the Java series of translators which are relied on quite heavily.
Attachments
Issue Links
- depends upon
-
TINKERPOP-3047 Grammar does not parse keywords into Map keys
- Open
-
TINKERPOP-3048 Class is not working right in language variants
- Open
-
TINKERPOP-3046 Make new keyword optional in Gremlin grammar
- Open
-
TINKERPOP-3043 Add BigDecimal support to JavaScript GLV
- Open
-
TINKERPOP-3044 Add the ability to explicitly specify the type for numeric data in JavaScript GLV
- Open
-
TINKERPOP-3041 Consistent construction of SeedStrategy
- Closed
- is related to
-
TINKERPOP-2653 ScriptTranslator for Java
- Open
-
TINKERPOP-2654 Add a GremlinLangTranslator
- Open
-
TINKERPOP-2714 Ensure that Gremlin translation matches its original form
- Open
- relates to
-
TINKERPOP-3084 Remove old Translator infrastructure
- Open
-
TINKERPOP-3085 Rewrite Translator documentation
- Open