Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Add a consistent schema format for TypedSchemaTransformProvider #31353

Open
16 tasks
chamikaramj opened this issue May 21, 2024 · 0 comments
Open
16 tasks
Assignees
Labels

Comments

@chamikaramj
Copy link
Contributor

What happened?

In b33a843 we reverted usage of snake case globally for TypedSchemaTransformProvider.

Creating this to track fixing this forward so that we maintain a consistent schema.

One way forward might be to re-introduce global snake case formatting to TypedSchemaTransformProvider but update the existing Beam provided TypedSchemaTransformProvider that needs to preserve backwards compatibility to use camel-case.

Issue Priority

Priority: 2 (default / most bugs 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: Spark Runner
  • Component: Flink Runner
  • Component: Samza Runner
  • Component: Twister2 Runner
  • Component: Hazelcast Jet Runner
  • Component: Google Cloud Dataflow Runner
@chamikaramj chamikaramj changed the title [Bug]: Add consistent schema format for TypedSchemaTransformProvider [Bug]: Add a consistent schema format for TypedSchemaTransformProvider May 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants