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.

Sign up for GitHub

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

Jump to bottom

[Bug]: starts.ApproximateQuantiles() sometimes returns one split potint when the number of requested quantiles is 1. #33449

Open
1 of 17 tasks
Labutin opened this issue Dec 26, 2024 · 0 comments
Open
1 of 17 tasks

[Bug]: starts.ApproximateQuantiles() sometimes returns one split potint when the number of requested quantiles is 1. #33449

Labutin opened this issue Dec 26, 2024 · 0 comments
Labels
awaiting triage bug go P2

Comments

@Labutin
Copy link

Labutin commented Dec 26, 2024

What happened?

I can't reproduce it each time when I run my program. But in 10% runs starts.ApproximateQuantiles() returns one split point when the number of requested quantiles is 1 when expected to get zero split points.

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
Assignees
No one assigned
Labels
awaiting triage bug go P2
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Labutin