Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: grouping with numpy.datetime64 keys gives silently incorrect behavior #33021

Closed
1 of 17 tasks
shoyer opened this issue Nov 5, 2024 · 0 comments
Closed
1 of 17 tasks

Comments

@shoyer
Copy link
Contributor

shoyer commented Nov 5, 2024

What happened?

All NumPy datetime64 values seem to get mapped to "not a time" (NaT):

import numpy as np
import apache_beam as beam
 
inputs = [(np.datetime64('2000-01-01'), 'first'), (np.datetime64('2000-01-02'), 'second')]
print(inputs | beam.GroupByKey())
# [(numpy.datetime64('NaT'), ['first', 'second'])]

This looks like potentially the same underlying issue as #33020 (incorrect handling of NumPy's int64, which gets mapped to zero)

Issue Priority

Priority: 2 (default / most bugs should be filed as P2)

Issue Components

  • Component: Python SDK
  • Component: Java SDK
  • Component: Go SDK
  • Component: Typescript SDK
  • Component: IO connector
  • Component: Beam YAML
  • Component: Beam examples
  • Component: Beam playground
  • Component: Beam katas
  • Component: Website
  • Component: Infrastructure
  • Component: Spark Runner
  • Component: Flink Runner
  • Component: Samza Runner
  • Component: Twister2 Runner
  • Component: Hazelcast Jet Runner
  • Component: Google Cloud Dataflow Runner
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants