[
https://issues.apache.org/jira/browse/TINKERPOP-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15882907#comment-15882907
]
ASF GitHub Bot commented on TINKERPOP-1639:
-------------------------------------------
Github user okram commented on the issue:
https://github.com/apache/tinkerpop/pull/564
@dkuppitz asked me to say more of my thoughts on the matter.
I think we need a general theory for how we are going to handle primitive
manipulations. That is, math operators, string operations, character
operations, type casting operations, etc.
If we just append this feature for `Strings` then we might end up
backtracking come a more general theory. It just seems that this PR is a "this
would be cool" and implemented. Not: "So, primitives all fit this style of
manipulation in a flow-based system..."
Questions that arise:
* What about `unfold()`? Now we are in character manipulation or just
single character strings?
* What about `fold()`? Does character folding become strings?
* What about `range()` on doubles/floats? Is that a way to clip precision?
I don't think we should just add this PR without a fully thought through
model for all primitives and how they will be effected by the current or "need
to be built" steps.
> Support simple String operations
> --------------------------------
>
> Key: TINKERPOP-1639
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1639
> Project: TinkerPop
> Issue Type: Improvement
> Components: process
> Affects Versions: 3.2.4
> Reporter: Daniel Kuppitz
> Assignee: Daniel Kuppitz
> Fix For: 3.3.0, 3.2.5
>
>
> Addd support for simple String operations, e.g. {{length()}} and
> {{substring()}}. The latter will also allow us to write {{startsWith()}} and
> {{endsWith()}} filters.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
