Laksh47 opened a new issue, #27728: URL: https://github.com/apache/beam/issues/27728
### What needs to happen? - Keep documentation consistent across SDKs - Java SDK docs [doesn't mention](https://beam.apache.org/releases/javadoc/current/org/apache/beam/sdk/io/gcp/datastore/DatastoreV1.Read.html#:~:text=If%20the%20query%20has%20a%20user%20limit%20set%2C%20then%20numQuerySplits%20will%20be%20ignored%20and%20no%20split%20will%20be%20performed) detail about inequality queries for `withNumQuerySplits` function - Python SDK docs [mention](https://beam.apache.org/releases/pydoc/current/apache_beam.io.gcp.datastore.v1new.datastoreio.html#:~:text=Any%20value%20of%20num_splits%20greater%20than%20ReadFromDatastore._NUM_QUERY_SPLITS_MAX%20will%20be%20capped%20at%20that%20value) the same here javadoc: <img width="1454" alt="Screenshot 2023-07-27 at 7 55 49 PM" src="https://github.com/apache/beam/assets/10058508/ba2c2820-d3b0-4f00-b07e-21df5bb81ab4";> pydoc: <img width="714" alt="Screenshot 2023-07-27 at 7 56 40 PM" src="https://github.com/apache/beam/assets/10058508/c25efcf9-03ff-460c-94f7-1f3cd017c55c";> context: faced this exception while running a dataflow job that utilizes this function <img width="858" alt="Screen Shot 2023-07-27 at 8 00 30 PM" src="https://github.com/apache/beam/assets/10058508/0d1e5904-58af-410c-8d97-2844ef0e252c";> ### Issue Priority Priority: 3 (nice-to-have improvement) ### Issue Components - [ ] Component: Python SDK - [X] Component: Java SDK - [ ] Component: Go SDK - [ ] Component: Typescript SDK - [ ] Component: IO connector - [ ] Component: Beam examples - [ ] Component: Beam playground - [ ] Component: Beam katas - [ ] Component: Website - [ ] Component: Spark Runner - [ ] Component: Flink Runner - [ ] Component: Samza Runner - [ ] Component: Twister2 Runner - [ ] Component: Hazelcast Jet Runner - [X] Component: Google Cloud Dataflow Runner -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
