emkornfield commented on pull request #10603: URL: https://github.com/apache/arrow/pull/10603#issuecomment-874423397
> Unless there's a context/use case I'm not thinking of (you'd know better than I @emkornfield), I don't like the idea of putting a check in the next function for this, but the only other thing i can think of would be to implement a way for the reader to essentially queue up the message it read in the case that it's not a schema message so that the next call to next() returns that first message before continuing to read from the stream, which I like better than checking on every call to next We have an api in [BQ](https://cloud.google.com/bigquery/docs/reference/storage) that returns a schema and then a stream of records separately. So its not so much replacing the schema as an easy way to provide a new one. Recently, we added in a returned schema on the [first ReadRows response](https://cloud.google.com/bigquery/docs/reference/storage/rpc/google.cloud.bigquery.storage.v1#google.cloud.bigquery.storage.v1.ReadRowsResponse). @shollyman would this make plumbing easier or obviate this change? -- 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]
