Repository navigation
[Task]: Update BigTable to Bigtable to match industry standards #40202
Description
What needs to happen?
Industry standards is to use lower "t" for "Table". So "Bigtable" instead of "BigTable".
- Double check non-yaml usage of "Bigtable" and ensure not "BigTable" - update BigTable to Bigtable for non-yaml related files #40207
- Correct usage in Yaml from "BigTable" to "Bigtable" for ReadFromBigTable and WriteToBigTable - fix Bigtable naming for yaml related files #40206
Issue Priority
Priority: 2 (default / most normal work should be filed as P2)
Issue Components
- Component: Python SDK
- Component: Java SDK
- Component: Go SDK
- Component: Typescript SDK
- Component: IO connector
- Component: Beam YAML
- Component: Beam examples
- Component: Beam playground
- Component: Beam katas
- Component: Website
- Component: Infrastructure
- Component: Spark Runner
- Component: Flink Runner
- Component: Prism Runner
- Component: Twister2 Runner
- Component: Hazelcast Jet Runner
- Component: Google Cloud Dataflow Runner
Activity
[-][Task]: Update ReadFromBigTable and WriteToBigTable naming to lower "t"[/-][+][Task]: Update BigTable to Bigtable to match industry standards[/+]derrickaw commentedon Sep 23, 2026
Reverted the Yaml changes as customer impact and little benefit. So this issue should just revolve around documentation changes only and that will be handled in the non-yaml changes only at this point.