[jira] [Commented] (NIFI-8336) Change bulletinTimestamp in QueryNiFi BULLETINS table to Long

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-8336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17303663#comment-17303663 ] 

ASF subversion and git services commented on NIFI-8336:
-------------------------------------------------------

Commit e16cc9df46bf46d461b605d3ca5ff29b18fe6a78 in nifi's branch refs/heads/main from Matt Burgess
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=e16cc9d ]

NIFI-8336: Change BULLETINS table bulletinTimestamp column to Long

Signed-off-by: Pierre Villard <pi...@gmail.com>

This closes #4909.


> Change bulletinTimestamp in QueryNiFi BULLETINS table to Long
> -------------------------------------------------------------
>
>                 Key: NIFI-8336
>                 URL: https://issues.apache.org/jira/browse/NIFI-8336
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Matt Burgess
>            Assignee: Matt Burgess
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> The table model for BULLETINS, which allows components like QueryNiFiReportingTask to issue SQL queries against NiFi repositories such as Bulletins, specifies the "bulletinTimestamp" column as a Date. 
> This makes it difficult to do comparisons, as Calcite (per the SQL standard) doesn't assume integral values correspond to dates/times based on Epoch. In order to get all bulletins after a certain Date (for example, five minutes ago), the user would have to do the math on the milliseconds and then format that as a String to be used as a Date literal in the SQL query.
> Instead this Jira proposes to change the datatype of bulletinTimestamp to "long", making it consistent with other table models' timestamp columns and making it easier to generate SQL queries using this field (such as incremental fetch).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)