[
https://issues.apache.org/jira/browse/BEAM-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mairbek Khadikov updated BEAM-3973:
-----------------------------------
Description: In 2.4.0, SpannerIO#read has been migrated to use batch API.
The batch API provides abstractions to scale out reads from Spanner, but it
requires the query to be root-partitionable. The root-partitionable queries
cover majority of the use cases, however there are examples when running
arbitrary query is useful. For example, reading all the table names from the
information_schema.* and reading the content of those tables in the next step.
(was: In 2.4.0, SpannerIO#read has been migrated to use batch API. The batch
API provides abstractions to scale out reads from Spanner, but it requires the
query to be root-partitionable. The root-partitionable queries cover majority
of the use cases, however there are examples when running arbitrary query is
useful. For example, reading all the tables from the information_schema.* and
reading the content of the schema schema in the next step. )
> Allow to disable batch API in SpannerIO
> ---------------------------------------
>
> Key: BEAM-3973
> URL: https://issues.apache.org/jira/browse/BEAM-3973
> Project: Beam
> Issue Type: Bug
> Components: io-java-gcp
> Affects Versions: 2.4.0
> Reporter: Mairbek Khadikov
> Assignee: Mairbek Khadikov
> Priority: Major
> Fix For: 2.5.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In 2.4.0, SpannerIO#read has been migrated to use batch API. The batch API
> provides abstractions to scale out reads from Spanner, but it requires the
> query to be root-partitionable. The root-partitionable queries cover majority
> of the use cases, however there are examples when running arbitrary query is
> useful. For example, reading all the table names from the
> information_schema.* and reading the content of those tables in the next
> step.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
