[jira] [Created] (FLINK-11960) Check all the builtin functions and operators are reasonable

Jark Wu created FLINK-11960: --- Summary: Check all the builtin functions and operators are reasonable Key: FLINK-11960 URL: https://issues.apache.org/jira/browse/FLINK-11960 Project: Flink Issue

[jira] [Created] (FLINK-11959) Introduce window operator for blink streaming runtime

Kurt Young created FLINK-11959: -- Summary: Introduce window operator for blink streaming runtime Key: FLINK-11959 URL: https://issues.apache.org/jira/browse/FLINK-11959 Project: Flink Issue

Re: [VOTE] Release 1.8.0, release candidate #2

I tested RC2 with the following items: - Maven Central Repository contains all artifacts - Built the source with Maven (ensured all source files have Apache headers) - Checked checksums and GPG files (for instance, flink-core-1.8.0.jar) that match the corresponding release files - Verified that

Re: [VOTE] Release 1.8.0, release candidate #2

Hi, The regressions in the benchmark were also brought up earlier in this thread by Yu. >From the previous investigations, these are the commits that touched relevant serializers (TupleSerializer, AvroSerializer, RowSerializer) around Jan / Feb: TupleSerializer - 73e4d0ecfd (Thu Feb 14 11:56:51

[jira] [Created] (FLINK-11958) flink on windows yarn deploy failed

Matrix42 created FLINK-11958: Summary: flink on windows yarn deploy failed Key: FLINK-11958 URL: https://issues.apache.org/jira/browse/FLINK-11958 Project: Flink Issue Type: Bug

Re: [DISCUSS] Create a Flink ecosystem website

Done. The writeup looks great! On Mon, Mar 18, 2019 at 9:09 PM Robert Metzger wrote: > Nice, really good news on the INFRA front! > I think the hardware specs sound reasonable. And a periodic backup of the > website's database to Infra's backup solution sounds reasonable too. > > Can you accept

[jira] [Created] (FLINK-11957) Expose failure cause in the API response when dispatcher fails to submit a job

Mark Cho created FLINK-11957: Summary: Expose failure cause in the API response when dispatcher fails to submit a job Key: FLINK-11957 URL: https://issues.apache.org/jira/browse/FLINK-11957 Project:

Re: [ANNOUNCEMENT] March 2019 Bay Area Apache Flink Meetup

Hi all, This is a reminder that the next Bay Area Flink Meetup is about one week away. Please RSVP if you plan to attend. Here is the list of the proposed talks: -- General community and project updates (Fabian Hueske) -- Real-time experimentation and beyond with Flink at Pinterest (Parag Kesar,

Re: [VOTE] Release 1.8.0, release candidate #2

Piotr and me discovered a possible issue in the benchmarks. Looking at the time graphs, there seems to be one issue coming around end of January. It increased network throughput, but decreased overall performance and added more variation in time (possibly through GC). Check the trend in these

[DISCUSS] Introduction of a Table API Java Expression DSL

Hi everyone, some of you might have already noticed the JIRA issue that I opened recently [1] about introducing a proper Java expression DSL for the Table API. Instead of using string-based expressions, we should aim for a unified, maintainable, programmatic Java DSL. Some background: The

Re: [VOTE] Release 1.8.0, release candidate #2

Watching the benchmark data for days and indeed it's normalized for the time being. However, the result seems to be unstable. I also tried the benchmark locally and observed obvious wave even with the same commit... I guess we may need to improve it such as increasing the RECORDS_PER_INVOCATION

Re: [VOTE] Release 1.8.0, release candidate #2

@Aljoscha I see, thanks for the quick response! Best Regards, Yu On Mon, 18 Mar 2019 at 19:11, Aljoscha Krettek wrote: > @Yu Thanks for the pointer. This is because I didn’t yet update the > buildbot configuration for the new release. It’s a point that is very low > in the release guide but I

Re: [DISCUSS] A more restrictive JIRA workflow

@Fabian: I don't think this is a big problem. Moving away from "giving everybody contributor permissions" to "giving it to some people" is not risky. I would leave this decision to the committers who are working with a person. We should bring this discussion to a conclusion and implement the

Re: [DISCUSS] Create a Flink ecosystem website

Nice, really good news on the INFRA front! I think the hardware specs sound reasonable. And a periodic backup of the website's database to Infra's backup solution sounds reasonable too. Can you accept and review my proposal for the website? On Sat, Mar 16, 2019 at 3:47 PM Becket Qin wrote: >

Re: [VOTE] Release 1.8.0, release candidate #2

Long term plan _is_ to move flink-shaded-hadoop to flink-shaded, I believe there's even a JIRA for that. Until that is in place they _must_ have retain the flink version as otherwise we'd be unable to change them in follow-up releases without changing the version scheme again. And even

Re: [VOTE] Release 1.8.0, release candidate #2

Additionally, which I fortunately did not realize earlier, we must also remove the "org.rocksdb:rocksdbjni" entry from the NOTICE files. (i.e. replace them with frocksdb) On 15.03.2019 15:35, Chesnay Schepler wrote: -1 Missing dependencies in NOTICE file of flink-dist (and by extension the

Re: [VOTE] Release 1.8.0, release candidate #2

Hi Chesnay, The artifacts to be released do not have a SNAPSHOT suffix: > > https://repository.apache.org/content/repositories/orgapacheflink-1213/org/apache/flink/flink-shaded-hadoop2-uber/ Thank you for providing this link. It's very useful for contributors who want to check the RC on YARN.

Re: [VOTE] Release 1.8.0, release candidate #2

@Yu Thanks for the pointer. This is because I didn’t yet update the buildbot configuration for the new release. It’s a point that is very low in the release guide but I think I’ll do that now. > On 18. Mar 2019, at 09:37, Yu Li wrote: > > One supplement for point #2: there's a Note on the doc

[jira] [Created] (FLINK-11956) Remove shading from filesystems build

Stefan Richter created FLINK-11956: -- Summary: Remove shading from filesystems build Key: FLINK-11956 URL: https://issues.apache.org/jira/browse/FLINK-11956 Project: Flink Issue Type:

[jira] [Created] (FLINK-11955) Modify build to move filesystems from lib to plugins folder

Stefan Richter created FLINK-11955: -- Summary: Modify build to move filesystems from lib to plugins folder Key: FLINK-11955 URL: https://issues.apache.org/jira/browse/FLINK-11955 Project: Flink

[jira] [Created] (FLINK-11953) Introduce Plugin/Loading system and integrate it with FileSystem

Stefan Richter created FLINK-11953: -- Summary: Introduce Plugin/Loading system and integrate it with FileSystem Key: FLINK-11953 URL: https://issues.apache.org/jira/browse/FLINK-11953 Project: Flink

[REMINDER] Please add entries for newly added dependencies to NOTICE file

Hi All, Please remember to add newly added dependencies to the NOTICE file of flink-dist (which will then end up in NOTICE-binary and so on). Discovering this late will cause delays in releases, as it is doing now. There is a handy guide that Chesnay and Till worked on that explains licensing

[jira] [Created] (FLINK-11954) Provide unit test(s) for new plugin infrastructure

Stefan Richter created FLINK-11954: -- Summary: Provide unit test(s) for new plugin infrastructure Key: FLINK-11954 URL: https://issues.apache.org/jira/browse/FLINK-11954 Project: Flink Issue

[jira] [Created] (FLINK-11952) Introduce Plugin Architecture for loading FileSystems

Stefan Richter created FLINK-11952: -- Summary: Introduce Plugin Architecture for loading FileSystems Key: FLINK-11952 URL: https://issues.apache.org/jira/browse/FLINK-11952 Project: Flink

[jira] [Created] (FLINK-11951) Enhance UserDefinedFunction interface to allow more user defined types

Jingsong Lee created FLINK-11951: Summary: Enhance UserDefinedFunction interface to allow more user defined types Key: FLINK-11951 URL: https://issues.apache.org/jira/browse/FLINK-11951 Project:

Re: [VOTE] Release 1.8.0, release candidate #2

One supplement for point #2: there's a Note on the doc for the error, but I'm wondering why we don't directly remove the -DarchetypeCatalog option in the command and tell users to specify the catalog in settings.xml if they prefer to. I mean, user tends to try the command first before checking the

Re: [VOTE] Release 1.8.0, release candidate #2

Issues observed when checking quick start: 1. The versions on the document are still "1.9-SNAPSHOT" instead of "1.8.0" 2. The "Use Maven archetypes" command failed with below error: [ERROR]

[jira] [Created] (FLINK-11950) Add missing dependencies in NOTICE file of flink-dist.

sunjincheng created FLINK-11950: --- Summary: Add missing dependencies in NOTICE file of flink-dist. Key: FLINK-11950 URL: https://issues.apache.org/jira/browse/FLINK-11950 Project: Flink Issue

Re: [VOTE] Release 1.8.0, release candidate #2

We release SNAPSHOT artifacts for all module, see https://repository.apache.org/content/groups/public/org/apache/flink/flink-core/ . The artifacts to be released do not have a SNAPSHOT suffix:

Re: [VOTE] Release 1.8.0, release candidate #2

-1 Currently, we have released the Hadoop-related JRA as a snapshot version(such as flink-shaded-hadoop2-uber/2.4.1-1.8-SNAPSHOT ), I think we should release a stable version. When testing the

[jira] [Created] (FLINK-11949) Introduce DeclarativeAggregateFunction and AggsHandlerCodeGenerator to blink planner

Jingsong Lee created FLINK-11949: Summary: Introduce DeclarativeAggregateFunction and AggsHandlerCodeGenerator to blink planner Key: FLINK-11949 URL: https://issues.apache.org/jira/browse/FLINK-11949