Skip to content

amazon_security_lake: tolerate non-ISO8601 in time_dt timestamps - #14799

Merged
efd6 merged 1 commit into
elastic:mainfrom
efd6:14588-amazon_security_lake
Aug 10, 2025
Merged

amazon_security_lake: tolerate non-ISO8601 in time_dt timestamps#14799
efd6 merged 1 commit into
elastic:mainfrom
efd6:14588-amazon_security_lake

Conversation

@efd6

@efd6 efd6 commented Aug 4, 2025

Copy link
Copy Markdown
Contributor

Proposed commit message

amazon_security_lake: tolerate non-ISO8601 in time_dt timestamps

The Go arrow parquet parser serialises timestamps into a non-conformant
format, 2006-01-02 15:04:05.999999999Z0700, resulting in date processor
failure. This has been fixed upstream and will be available in a future
version of the package. In the mean time, tolerate the format that they
emit.

Note that the long optional chain is required because the 9s fractional
specification in the serialisation indicates that the marshaler will
truncate trailing zero digits[1].

[1]https://pkg.go.dev/time

Checklist

  • I have reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.
  • I have verified that Kibana version constraints are current according to guidelines.
  • I have verified that any added dashboard complies with Kibana's Dashboard good practices

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Screenshots

@efd6 efd6 self-assigned this Aug 4, 2025
@efd6 efd6 added enhancement New feature or request Integration:amazon_security_lake Amazon Security Lake Team:Security-Service Integrations Security Service Integrations team [elastic/security-service-integrations] labels Aug 4, 2025
The Go arrow parquet parser serialises timestamps into a non-conformant
format, 2006-01-02 15:04:05.999999999Z0700, resulting in date processor
failure. This has been fixed upstream and will be available in a future
version of the package. In the mean time, tolerate the format that they
emit.

Note that the long optional chain is required because the 9s fractional
specification in the serialisation indicates that the marshaler will
truncate trailing zero digits[1].

[1]https://pkg.go.dev/time
@efd6
efd6 force-pushed the 14588-amazon_security_lake branch from ac002a6 to a74bee5 Compare August 4, 2025 23:54
@elastic-vault-github-plugin-prod

Copy link
Copy Markdown
Contributor

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

@elasticmachine

Copy link
Copy Markdown

�� Build Succeeded

cc @efd6

@elastic-sonarqube

Copy link
Copy Markdown

Quality Gate failed Quality Gate failed

Failed conditions
25.2% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube

@efd6
efd6 marked this pull request as ready for review August 5, 2025 00:21
@efd6
efd6 requested a review from a team as a code owner August 5, 2025 00:21
@elasticmachine

Copy link
Copy Markdown

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

@efd6
efd6 merged commit b73d57c into elastic:main Aug 10, 2025
8 of 9 checks passed
@elastic-vault-github-plugin-prod

Copy link
Copy Markdown
Contributor

Package amazon_security_lake - 2.7.0 containing this change is available at https://epr.elastic.co/package/amazon_security_lake/2.7.0/

robester0403 pushed a commit to robester0403/integrations that referenced this pull request Aug 14, 2025
…stic#14799)

The Go arrow parquet parser serialises timestamps into a non-conformant
format, 2006-01-02 15:04:05.999999999Z0700, resulting in date processor
failure. This has been fixed upstream and will be available in a future
version of the package. In the mean time, tolerate the format that they
emit.

Note that the long optional chain is required because the 9s fractional
specification in the serialisation indicates that the marshaler will
truncate trailing zero digits[1].

[1]https://pkg.go.dev/time
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request Integration:amazon_security_lake Amazon Security Lake Team:Security-Service Integrations Security Service Integrations team [elastic/security-service-integrations]

3 participants