[
https://issues.apache.org/jira/browse/METRON-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15735553#comment-15735553
]
ASF GitHub Bot commented on METRON-616:
---------------------------------------
Github user ottobackwards commented on the issue:
https://github.com/apache/incubator-metron/pull/392
So - the case I am thinking of is a stellar transform on an incoming string
field that contains a number, but that number will not be marked - so only
doubles would work unless I'm mistaken. I am not sure that requiring the
fields to be marked up works so well when you don't have control of the sources.
By specifying TO_XXXX are you explicitly saying you want it treated at a
string of number marked as type? Why impose the restriction of having to have
the string marked?
> Add Support in Stellar for Long and Float Literals
> --------------------------------------------------
>
> Key: METRON-616
> URL: https://issues.apache.org/jira/browse/METRON-616
> Project: Metron
> Issue Type: Improvement
> Reporter: Josh Meyer
>
> Currently Stellar only supports literals for doubles and integers. However,
> it is possible for functions to return longs and floats. An example, are the
> timestamp functions. These will return a long. It would be useful for a
> Stellar user to also use Java style floats and longs (eg. 3L, 3F, 3.3f,
> etc.).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
