[
https://issues.apache.org/jira/browse/NIFI-2737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15571932#comment-15571932
]
Matt Burgess commented on NIFI-2737:
------------------------------------
What kind of column types and rollover do you envision? For a time dimension,
the entries for things like day of month, month, and year are likely integers,
but the processor would need to know that month rolls over at value 12, etc.
For pure types like Integer, even with variable length, we could calculate the
maximum possible value, but that's the only use case I can think of without
adding many more properties (likely dynamic) for the user to indicate rollover
values for max-value columns. Not saying it's a bad idea, just want to hear
your thoughts on the approach :)
> Max Value Column in QueryDatabaseTable/GenerateTableFetch need to handle
> rollover
> ---------------------------------------------------------------------------------
>
> Key: NIFI-2737
> URL: https://issues.apache.org/jira/browse/NIFI-2737
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Jeff Storck
> Priority: Minor
> Fix For: 1.1.0
>
>
> QueryDatabaseTable and GenerateTableFetch should support the case where a max
> value column rolls over.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
