stankiewicz commented on PR #38056: URL: https://github.com/apache/beam/pull/38056#issuecomment-4205636224
> I’ve learned from the Bigtable product team that Materialized Views currently return [structured row keys](https://docs.cloud.google.com/bigtable/docs/structured-row-key-queries) without a public decoding mapping. This makes it impossible to process row keys in Beam as originally intended. Reading all records is possible but reading row ranges is not reliably possible. > > I’m putting this PR on hold until that prerequisite is addressed service-side, unless anyone with knowledge about this sees any other option to proceed without the structured row keys in place. > > A [workaround](https://github.com/apache/beam/issues/38053#issuecomment-4203569927) is documented in the associated issue with this PR so the prerequisite is providing client library that will allow serializing `structured row key` into ByteKey so the range scans work. That would need providing row key schema as it is not only delimiter but also there is plenty of flexibility in encoding. -- 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]
