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
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
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
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
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
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
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
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
> > 在
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]
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
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:
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
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
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
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:
+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
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,
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
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
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
+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
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:
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:
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
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
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:
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
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
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
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
>
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
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
Thanks for the response @Robert
It’s helpful, I’ll try your advice.
Best,
Leonard
> 在 2020年5月22日，14:04，Robert Metzger 写道：
>
> Hi Leonard,
>
> for the first problem, I reported this to Microsoft a while ago, and they
> acknowledged that it is a valid problem that they are going to address
Hi,
Quick update on the release. After the feature freeze me and Zhijiang were
reached out by quite a bit of contributors, which had features in "almost
done" state and were asking for permission to merge them after the
announced release branch cut and in most cases we granted this permission.
As
Wei Zhong created FLINK-17876:
-
Summary: Add documents for the Python UDF SQL DDL.
Key: FLINK-17876
URL: https://issues.apache.org/jira/browse/FLINK-17876
Project: Flink
Issue Type: Improvement
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 Flink contributors, which leads to cases where
I spend quite some time on filling the fields correctly (at least
Hi Leonard,
for the first problem, I reported this to Microsoft a while ago, and they
acknowledged that it is a valid problem that they are going to address [1].
In the meantime, you can manually access the overview of all "master" and
"release-1.11" builds here:
37 matches
Mail list logo
