You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The parseDefaultExpression function is missing implementations for the following ClickHouse types:
DateTime
Array
Tuple
Float32
Float64
This omission results in errors or unhandled cases when attempting to parse default expressions for these types.
Suggested Improvement:
Generalize the parseDefaultExpression function to handle any string-based conversion into the appropriate Java representation that ClickHouse expects. This would make the function more robust and capable of supporting future type additions without requiring frequent updates.
Steps to Reproduce:
Call the parseDefaultExpression function with a value and a column type that matches any of the unsupported types listed above.
Observe that the function either fails or returns an incorrect result.
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: Infrastructure
Component: Spark Runner
Component: Flink Runner
Component: Samza Runner
Component: Twister2 Runner
Component: Hazelcast Jet Runner
Component: Google Cloud Dataflow Runner
The text was updated successfully, but these errors were encountered:
What happened?
The parseDefaultExpression function is missing implementations for the following ClickHouse types:
DateTime
Array
Tuple
Float32
Float64
This omission results in errors or unhandled cases when attempting to parse default expressions for these types.
Suggested Improvement:
Generalize the parseDefaultExpression function to handle any string-based conversion into the appropriate Java representation that ClickHouse expects. This would make the function more robust and capable of supporting future type additions without requiring frequent updates.
Steps to Reproduce:
Call the parseDefaultExpression function with a value and a column type that matches any of the unsupported types listed above.
Observe that the function either fails or returns an incorrect result.
Issue Priority
Priority: 2 (default / most bugs should be filed as P2)
Issue Components
The text was updated successfully, but these errors were encountered: