Re: [DISCUSS] Semantics of our JIRA fields

Thanks for bringing this up, Robert. +1 from my side on your proposal. Additionally, there's one question that I would appreciate if someone can clarify them. When talking about "all currently supported and unreleased Flink versions", *which versions are supported and which are not? *I've heard

[jira] [Created] (FLINK-17877) Add support for Python 3.8

Robert Metzger created FLINK-17877: -- Summary: Add support for Python 3.8 Key: FLINK-17877 URL: https://issues.apache.org/jira/browse/FLINK-17877 Project: Flink Issue Type: Improvement

Re: [DISCUSS] Semantics of our JIRA fields

Thanks for your response! The information about supported Flink releases is quite hidden, but it is on the downloads page in the "Update Policy for old releases" section, and it states: As of March 2017, the Flink community decided >

[jira] [Created] (FLINK-17878) StreamingFileWriter watermark attribute is transient, this might be different with origin value

xiaogang zhou created FLINK-17878: - Summary: StreamingFileWriter watermark attribute is transient, this might be different with origin value Key: FLINK-17878 URL: https://issues.apache.org/jira/browse/FLINK-17878

[jira] [Created] (FLINK-17879) Update Python row serializer

Timo Walther created FLINK-17879: Summary: Update Python row serializer Key: FLINK-17879 URL: https://issues.apache.org/jira/browse/FLINK-17879 Project: Flink Issue Type: Improvement

[jira] [Created] (FLINK-17880) Use new type inference for SQL table and scalar functions

Timo Walther created FLINK-17880: Summary: Use new type inference for SQL table and scalar functions Key: FLINK-17880 URL: https://issues.apache.org/jira/browse/FLINK-17880 Project: Flink Iss

[jira] [Created] (FLINK-17881) Add documentation for PyFlink's Windows support

Wei Zhong created FLINK-17881: - Summary: Add documentation for PyFlink's Windows support Key: FLINK-17881 URL: https://issues.apache.org/jira/browse/FLINK-17881 Project: Flink Issue Type: Improve

Re: [DISCUSS] Semantics of our JIRA fields

Thanks for driving this discussion, Robert. +1 for the proposal. Best, Yangze Guo On Fri, May 22, 2020 at 3:32 PM Robert Metzger wrote: > > Thanks for your response! > > The information about supported Flink releases is quite hidden, but it is > on the downloads page in the "Update Policy for

Re: [DISCUSS] Semantics of our JIRA fields

Thanks for the pointer. That's clear enough for me. Thank you~ Xintong Song On Fri, May 22, 2020 at 3:32 PM Robert Metzger wrote: > Thanks for your response! > > The information about supported Flink releases is quite hidden, but it is > on the downloads page in the "Update Policy for old re

[jira] [Created] (FLINK-17882) Don't allow self referencing structured type

Timo Walther created FLINK-17882: Summary: Don't allow self referencing structured type Key: FLINK-17882 URL: https://issues.apache.org/jira/browse/FLINK-17882 Project: Flink Issue Type: Sub-

[jira] [Created] (FLINK-17883) Unable to configure write mode for FileSystem() connector in PyFlink

Robert Metzger created FLINK-17883: -- Summary: Unable to configure write mode for FileSystem() connector in PyFlink Key: FLINK-17883 URL: https://issues.apache.org/jira/browse/FLINK-17883 Project: Fli

Re: [DISCUSS] Semantics of our JIRA fields

+1 Thanks Robert for these detailed explanations! It is definitely useful to have a clear standard to avoid confusion when creating Jira, especially for starters. Thanks for the efforts! Best, Yuan On Fri, May 22, 2020 at 2:07 PM Robert Metzger wrote: > Hi all, > > I have the feeling that the

[jira] [Created] (FLINK-17884) package the codegen directory to flink-sql-parser jar

zhanghang-dev created FLINK-17884: - Summary: package the codegen directory to flink-sql-parser jar Key: FLINK-17884 URL: https://issues.apache.org/jira/browse/FLINK-17884 Project: Flink Issue

[jira] [Created] (FLINK-17885) StreamingFileCommitter watermark attribute is transient, this might be different with origin value

Yichao Yang created FLINK-17885: --- Summary: StreamingFileCommitter watermark attribute is transient, this might be different with origin value Key: FLINK-17885 URL: https://issues.apache.org/jira/browse/FLINK-17885

Re: [DISCUSS] Semantics of our JIRA fields

Thanks Robert for bringing up this. +1 to the proposal. >From my perspective, I would like we can clearify one more thing about "fix version/s" in this wiki. IIRC, if a fix is targeted to be fixed in "1.11.0", then it obviously is fixed in "1.12.0", so such a bug fix should only set "1.11.0", not

Re: [DISCUSS] Semantics of our JIRA fields

Thanks for bringing up this discussion, Robert. +1 to the proposal, it's very clear. > 在 2020年5月22日，下午7:50，Jark Wu 写道： > > Thanks Robert for bringing up this. +1 to the proposal. > > From my perspective, I would like we can clearify one more thing about "fix > version/s" in this wiki. > IIRC,

Re: [DISCUSS] Semantics of our JIRA fields

+1 That's also how I think of the semantics of the fields. Aljoscha On 22.05.20 08:07, Robert Metzger wrote: Hi all, I have the feeling that the semantics of some of our JIRA fields (mostly "affects versions", "fix versions" and resolve / close) are not defined in the same way by all the core

[jira] [Created] (FLINK-17886) Update documentation for new WatermarkGenerator/WatermarkStrategies

Aljoscha Krettek created FLINK-17886: Summary: Update documentation for new WatermarkGenerator/WatermarkStrategies Key: FLINK-17886 URL: https://issues.apache.org/jira/browse/FLINK-17886 Project:

[jira] [Created] (FLINK-17887) Improve interface of ScanFormatFactory and SinkFormatFactory

Jark Wu created FLINK-17887: --- Summary: Improve interface of ScanFormatFactory and SinkFormatFactory Key: FLINK-17887 URL: https://issues.apache.org/jira/browse/FLINK-17887 Project: Flink Issue Typ

Re: [DISCUSS] Semantics of our JIRA fields

Thanks bringing up this topic @Robert, +1 to the proposal. It clarifies the JIRA fields well and should be a rule to follow. Best, Leonard Xu > 在 2020年5月22日，20:24，Aljoscha Krettek 写道： > > +1 That's also how I think of the semantics of the fields. > > Aljoscha > > On 22.05.20 08:07, Robert Me

[jira] [Created] (FLINK-17888) JDBC Connector support LocalDateTime type

forideal created FLINK-17888: Summary: JDBC Connector support LocalDateTime type Key: FLINK-17888 URL: https://issues.apache.org/jira/browse/FLINK-17888 Project: Flink Issue Type: Task

[jira] [Created] (FLINK-17889) flink-connector-hive jar contains wrong class in its SPI config file org.apache.flink.table.factories.TableFactory

Jeff Zhang created FLINK-17889: -- Summary: flink-connector-hive jar contains wrong class in its SPI config file org.apache.flink.table.factories.TableFactory Key: FLINK-17889 URL: https://issues.apache.org/jira/browse

[jira] [Created] (FLINK-17890) support in DataType TIMESTAMP_WITH_LOCAL_TIME_ZONE in JDBC

Leonard Xu created FLINK-17890: -- Summary: support in DataType TIMESTAMP_WITH_LOCAL_TIME_ZONE in JDBC Key: FLINK-17890 URL: https://issues.apache.org/jira/browse/FLINK-17890 Project: Flink Issue

Re: Issues using StreamingFileSink (Cannot locate configuration: tried hadoop-metrics2-s3a-file-system.properties, hadoop-metrics2.properties)

Hi, for the first message I think this might be related to BEANUTILS-477 [1] and should not be a problem. The other messages look to me like the metric system initialization of the Hadoop components. I don't think that there is something wrong with them. [1] https://issues.apache.org/jira/browse

Re: [DISCUSS] Semantics of our JIRA fields

Thanks for drafting this proposal Robert. +1 for the proposal. Cheers, Till On Fri, May 22, 2020 at 5:39 PM Leonard Xu wrote: > Thanks bringing up this topic @Robert, +1 to the proposal. > > It clarifies the JIRA fields well and should be a rule to follow. > > Best, > Leonard Xu > > 在 2020年5月2

[jira] [Created] (FLINK-17891) FlinkYarnSessionCli sets wrong execution.target type

Shangwen Tang created FLINK-17891: - Summary: FlinkYarnSessionCli sets wrong execution.target type Key: FLINK-17891 URL: https://issues.apache.org/jira/browse/FLINK-17891 Project: Flink Issue

[jira] [Created] (FLINK-17892) Dynamic option may not be a part of the table digest

hailong wang created FLINK-17892: Summary: Dynamic option may not be a part of the table digest Key: FLINK-17892 URL: https://issues.apache.org/jira/browse/FLINK-17892 Project: Flink Issue Ty

[jira] [Created] (FLINK-17893) SQL-CLI no exception stack

Jingsong Lee created FLINK-17893: Summary: SQL-CLI no exception stack Key: FLINK-17893 URL: https://issues.apache.org/jira/browse/FLINK-17893 Project: Flink Issue Type: Bug Componen

[jira] [Created] (FLINK-17894) RowGenerator in datagen connector should be serializable

Jingsong Lee created FLINK-17894: Summary: RowGenerator in datagen connector should be serializable Key: FLINK-17894 URL: https://issues.apache.org/jira/browse/FLINK-17894 Project: Flink Issu

[jira] [Created] (FLINK-17895) Default value of rows-per-second in datagen should be limited

Jingsong Lee created FLINK-17895: Summary: Default value of rows-per-second in datagen should be limited Key: FLINK-17895 URL: https://issues.apache.org/jira/browse/FLINK-17895 Project: Flink

[jira] [Created] (FLINK-17896) HiveCatalog can work with new table factory because of is_generic

Jingsong Lee created FLINK-17896: Summary: HiveCatalog can work with new table factory because of is_generic Key: FLINK-17896 URL: https://issues.apache.org/jira/browse/FLINK-17896 Project: Flink

Shall we avoid binding "unsafe ports" during random port selection?

Hi dev, Recently we have found that when* `rest.bind-port`* parameter is specified as a port range (i.e. "5000-8000"), Flink may bind to some port (like 6000) that is not allowed by Chrome (showing a "ERR_UNSAFE_PORT" message and preventing users to continue accessing the website), similarly Firef