[Spanner] Is partitionQuery() dropping `dataBoostEnabled` intentional?

[dkkoma]

Version

google/cloud-spanner : v2.10.0

Question

BatchSnapshot::partitionQuery() / partitionRead() document a dataBoostEnabled option.
However, Operation::partitionQuery() seems to build the returned partition's options via pluckArray(['parameters', 'types', 'maxPartitions', 'partitionSizeBytes'], $options), which excludes dataBoostEnabled.

As a result, it never reaches the ExecuteSqlRequest in executePartition() (data_boost_enabled stays false), so partitioned queries run on standard compute without error.