[ 
https://issues.apache.org/jira/browse/FLINK-31174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Flink Jira Bot updated FLINK-31174:
-----------------------------------
    Labels: pull-request-available stale-minor  (was: pull-request-available)

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.


> [Doc] Inconsistent data format between flink-training-repo and learn-flink doc
> ------------------------------------------------------------------------------
>
>                 Key: FLINK-31174
>                 URL: https://issues.apache.org/jira/browse/FLINK-31174
>             Project: Flink
>          Issue Type: Improvement
>          Components: Documentation / Training
>    Affects Versions: 1.16.1
>            Reporter: CHEN Zhongpu
>            Priority: Minor
>              Labels: pull-request-available, stale-minor
>
> The data format specified in 
> [flink-training-repo|[https://github.com/apache/flink-training/tree/release-1.16]]
>  shows that a TaixRide is either a start or an end one with the eventTime.
> However, the Java code in [Data Pipelines & 
> ETL|[https://nightlies.apache.org/flink/flink-docs-release-1.16/docs/learn-flink/etl/]]
>   tried to get both "startTime" and "endTime". But in fact, those are not 
> defined in flink-training-repo.
> {code:java}
> Interval rideInterval = new Interval(ride.startTime, ride.endTime); {code}
> I think such inconsistency would puzzle new comers of Flink.
> According to the mail list discussion, it is due to a new 
> [pr|[https://github.com/apache/flink-training/pull/36]] and the doc forgets 
> to update. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to