[
https://issues.apache.org/jira/browse/FLINK-18180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-18180:
-----------------------------------
Labels: auto-deprioritized-major stale-minor (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> unify the logic of time attribute derivation for both batch and streaming
> -------------------------------------------------------------------------
>
> Key: FLINK-18180
> URL: https://issues.apache.org/jira/browse/FLINK-18180
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Planner
> Reporter: godfrey he
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> Currently, the logic of time attribute derivation is different for batch and
> streaming. For batch table source, the rowtime type will not be generated or
> will be erased as regular time type if the source table has rowtime type. To
> handle this difference, we have to distinguish batch or streaming via
> {{isStreamingMode}} flag in many places, such as: {{DatabaseCalciteSchema}},
> {{CatalogSchemaTable}}, {{CatalogTableSchemaResolver}}, etc. In fact, batch
> queries may also need rowtime type, such as supporting rowtime temporal join.
> So we can unify the logic of time attribute derivation from the source side,
> and erase the rowtime type if need in optimization phase. And then it's
> easier to push the unified {{TableEnvironment}} and planner forward.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
