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

Allow timestamp type to be inferred when using schema inference #7730

Closed
colinhicks opened this issue Jun 25, 2021 · 0 comments · Fixed by #7737
Closed

Allow timestamp type to be inferred when using schema inference #7730

colinhicks opened this issue Jun 25, 2021 · 0 comments · Fixed by #7737
Assignees
Labels
enhancement streaming-engine Tickets owned by the ksqlDB Streaming Team
Milestone

Comments

@colinhicks
Copy link
Member

Is your feature request related to a problem? Please describe.
Currently schemas that are tagged with timestamp metadata are inferred with the bigint type. For example, when schema inference is used when the input topic schema contains a timestamp-tagged Avro record field:

{
  "name": "XYZ",
  "type": {
    "connect.name": "org.apache.kafka.connect.data.Timestamp",
    "connect.version': 1,
    "logicalType": "timestamp-millis",
    "type": "long"
  }
}

... a respective stream created using schema inference would use BIGINT for the XYZ column.

Describe the solution you'd like
Schemas tagged with timestamp metadata should be inferred with the ksqlDB timestamp type.

@colinhicks colinhicks added enhancement needs-triage streaming-engine Tickets owned by the ksqlDB Streaming Team labels Jun 25, 2021
@jzaralim jzaralim self-assigned this Jun 28, 2021
@vcrfxia vcrfxia added this to the 0.20.0 milestone Jun 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement streaming-engine Tickets owned by the ksqlDB Streaming Team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants