Hi,
I want to contribute to Apache Flink.
Would you please give methe contributor permission?
My JIRA ID is LouisXu777.
--
徐小斌 LouisXu
Email:xu_soft39211...@163.com
QQ:2565641481
Telephone:15210968903
@北京航空航天大学
You now have contributor permissions.
On 14.03.2019 10:42, 徐小斌 wrote:
Hi,
I want to contribute to Apache Flink.
Would you please give methe contributor permission?
My JIRA ID is LouisXu777.
--
徐小斌 LouisXu
Email:xu_soft39211...@163.com
QQ:2565641481
Telephone:15210968903
@北京航空航天大学
Hi jingcheng,
Thanks for bringing up the detailed design. I think the column operation
feature is a great improvement to Table API.
+1 to the design from my side.
I only left a minor comment in the google doc.
Looking forward to the feature.
Best,
Jark
On Mon, 11 Mar 2019 at 12:29, jincheng
thinktothings created FLINK-11919:
-
Summary: Exception in thread "main"
org.apache.flink.table.api.SqlParserException: SQL parse failed. Encountered
"FROM user" at line 1, column 17.
Key: FLINK-11919
URL:
Chesnay Schepler created FLINK-11920:
Summary: EnumValueSerializerUpgradeTest fails on Java 9
Key: FLINK-11920
URL: https://issues.apache.org/jira/browse/FLINK-11920
Project: Flink
Issue
Chesnay Schepler created FLINK-11923:
Summary: Move reporter instantiation into
MetricRegistryConfiguration
Key: FLINK-11923
URL: https://issues.apache.org/jira/browse/FLINK-11923
Project: Flink
Timo Walther created FLINK-11921:
Summary: Upgrade Calcite dependency to 1.19
Key: FLINK-11921
URL: https://issues.apache.org/jira/browse/FLINK-11921
Project: Flink
Issue Type: Improvement
Thanks for writing up the specifications.
Regarding the website source code, Austin found a website[1] whose frontend
code[2] is available publicly. It lacks some support (e.g login), but it is
still a good starting point. One thing is that I did not find a License
statement for that source code.
Chesnay Schepler created FLINK-11922:
Summary: Support MetricReporter factories
Key: FLINK-11922
URL: https://issues.apache.org/jira/browse/FLINK-11922
Project: Flink
Issue Type: New
Hi everyone,
Please review and vote on the release candidate 2 for Flink 1.8.0, as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)
The complete staging area is available for your review, which includes:
* JIRA release notes [1],
* the
Hi Robert,
I also like the idea of making every Jira user an "Assignable User", but
restrict assigning a ticket to people with committer permissions.
Instead of giving contributor permissions to everyone, we could have a
more staged approach from user, to contributor, and finally to
Thanks Piotr, for the +1 and all the patient discussion :)
On Wed, Mar 13, 2019 at 3:53 PM Piotr Nowojski wrote:
> Hi Becket,
>
> Thank you for driving the effort and writing down the detailed proposal.
> To me this FLIP looks good and it has +1 from me.
>
> Piotr Nowojski
>
> > On 12 Mar 2019,
thinktothings created FLINK-11924:
-
Summary: Exception in thread "main"
org.apache.flink.table.api.SqlParserException: SQL parse failed. Encountered
"EXISTS" at line 1, column 40.
Key: FLINK-11924
URL:
Hi Aljoscha and all,
>From our performance benchmark web site (
http://codespeed.dak8s.net:8000/changes/) I observed a noticeable
regression (-6.92%) on the serializerAvro case comparing the latest 100
revisions, which may need some attention. Thanks.
Best Regards,
Yu
On Thu, 14 Mar 2019 at
@Yu
Thanks for reporting that Yu, great that this was noticed.
The serializerAvro case seems to only be testing on-wire serialization.
I checked the changes to the `AvroSerializer`, and it seems like
FLINK-11436 [1] with commit 479ebd59 was the only change that may have
affected that.
That commit
Tzu-Li (Gordon) Tai created FLINK-11925:
---
Summary: KryoSerializerSnapshot doesn't completely capture state /
configuration of Kryo instance
Key: FLINK-11925
URL:
16 matches
Mail list logo