jnturton commented on issue #2788: URL: https://github.com/apache/drill/issues/2788#issuecomment-1498952911
Thank you, it's always nice to receive a high quality report like this. Drill does only support millisecond precision in its TIMESTAMP type and it does handle timestamps that have greater precision by flooring to the nearest millisecond (or by sending them to a BIGINT instead). So I think your fix is on the right track. This definitely merits an issue in [the Apache Jira](https://issues.apache.org/). IIRC, to combat spammers you may now have to request a Jira account which we approve but we'll keep an eye open for that. Once we've got a DRILL-nnnn number we can base your PR on it and I'll take a closer look at the fix in review. We can also close this GitHub issue wtih a comment like "Promoted to DRILL-nnnn". -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@drill.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
