METRON-1816: Date format Stellar function #1233
Conversation
Looks like a very useful gap filler to me. +1 (non-binding) by inspection from me for sure. |
we should support the ISO date format constants so that users don't have to copy those formats. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a couple of questions
public static String getDateFormat(String format, Optional<Long> epochTime, Optional<String> timezone) { | ||
Long time = epochTime.orElseGet(System::currentTimeMillis); | ||
TimezonedFormat fmt = timezone.map(s -> new TimezonedFormat(format, s)).orElseGet(() -> new TimezonedFormat(format)); | ||
SimpleDateFormat sdf = formatCache.get(fmt).get(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
are there any errors we need to wrap here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are no exceptions thrown by any calls in this method. What are you thinking we should do?
@Test(expected = ParseException.class) | ||
public void testDateFormatNull() { | ||
Object result = run("DATE_FORMAT('EEE MMM dd yyyy hh:mm:ss zzz', nada, 'EST')"); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we have a test for an invalid format
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
@ottobackwards wouldn't ISO constant support require us to do a check on the string before passing to the DateFormat instance, which on something that is likely to be run A LOT (i.e. multiple times for every message) could actually be a significant for performance, which I would say outweighs the convenience of not having to remember what the format looks like. |
I'm not sure what you mean? Can you elaborate? https://docs.oracle.com/javase/8/docs/api/java/time/format/DateTimeFormatter.html |
I would worry about having to parse the strong argument to determine whether to use a constant or custom formatter, but I guess my concern is limited because we’re caching the formatter anyway so maybe I’m just over thinking it. Just very conscious we should keep performance at front of mind for this. |
This comes to mind for me, because using Nifi processors that take date formats and in other places I'm sick of cutting and pasting complex ISO formats into configurations when there are named formatters in java. This is just a suggestion, not a blocker. |
Right, I hear that! I also really like the idea of a follow on function that returns the default formats as a great solution to this problem. Should we do that? |
The existing Stellar date functions use SimpleDateFormat and already have a caching layer built in so I decided to reuse what was already there. Happy to switch to DateTimeFormatter here or in a follow on. |
+1 |
Contributor Comments
This PR adds a Stellar function that wraps the Java SimpleDateFormat class. The first argument is a date format string and is required. The second argument is epoch time and is optional (defaults to current time). The third argument is a timezone and is also option (default time zone of the environment is used if missing).
Testing
This has been tested in full dev:
DATE_FORMAT
function should be available:DATE_FORMAT
function to format the value in the epoch field created in the previous step. The result should be a correctly formatted date that matches the format string, epoch time and timezone:Pull Request Checklist
Thank you for submitting a contribution to Apache Metron.
Please refer to our Development Guidelines for the complete guide to follow for contributions.
Please refer also to our Build Verification Guidelines for complete smoke testing guides.
In order to streamline the review of the contribution we ask you follow these guidelines and ask you to double check the following:
For all changes:
For code changes:
Have you included steps to reproduce the behavior or problem that is being changed or addressed?
Have you included steps or a guide to how the change may be verified and tested manually?
Have you ensured that the full suite of tests and checks have been executed in the root metron folder via:
Have you written or updated unit tests and or integration tests to verify your changes?
If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent?
For documentation related changes:
Have you ensured that format looks appropriate for the output in which it is rendered by building and verifying the site-book? If not then run the following commands and the verify changes via
site-book/target/site/index.html
:Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.
It is also recommended that travis-ci is set up for your personal repository such that your branches are built there before submitting a pull request.