[
https://issues.apache.org/jira/browse/MINIFICPP-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Zink updated MINIFICPP-2063:
-----------------------------------
Description:
RFC3339 complient strings can be tricky to parse with expression language,
because it accepts a lot of formats and toDate can only handle one specific
format specifier.
It would be nice if we had an expression language function that handles all
compliant string representations so we can parse them regardless of source.
ListenSyslog parsed messages are one example where the timestamp comes from
thirdparty applications and is semi regulated (it uses the subset of RFC3339).
was:
RFC3339 complient strings can be tricky to parse with expression language,
because it accepts a lot of formats and toDate can only handle one specific
format specifier.
It would be nice if we had an expression language function that handles all
complient string representations so we can parse them regardless of source.
ListenSyslog parsed messages are one example where the timestamp comes from
thirdparty applications and is semi regulated (it uses the subset of RFC3339).
> RFC3339 parsing with expression language
> ----------------------------------------
>
> Key: MINIFICPP-2063
> URL: https://issues.apache.org/jira/browse/MINIFICPP-2063
> Project: Apache NiFi MiNiFi C++
> Issue Type: Improvement
> Reporter: Martin Zink
> Assignee: Martin Zink
> Priority: Major
>
> RFC3339 complient strings can be tricky to parse with expression language,
> because it accepts a lot of formats and toDate can only handle one specific
> format specifier.
> It would be nice if we had an expression language function that handles all
> compliant string representations so we can parse them regardless of source.
> ListenSyslog parsed messages are one example where the timestamp comes from
> thirdparty applications and is semi regulated (it uses the subset of RFC3339).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
