Re: [外部邮件] Re: Question about type cast in ExpressionReducer's reduce procedure

Hi Jark Wu, I did see the wrong result type failed the CodeGen compile stage, it throws out exception stack as follow, even before the ExpressionReducer actually restores the origin return type: org.apache.flink.api.common.InvalidProgramException: Table program cannot be compiled. T

Re: Question about type cast in ExpressionReducer's reduce procedure

Hi Aegeaner, First of all, the ExpressionReducer actually restores the origin return type after reducing, see https://github.com/apache/flink/blob/master/flink-libraries/flink-table/src/main/scala/org/apache/flink/table/codegen/ExpressionReducer.scala#L122 So the reduced result and type should be

Question about type cast in ExpressionReducer's reduce procedure

Hi all, I am implementing a STR_TO_DATE scalar SQL function to flink, and found return type casted from java.sql.Date to Integer in Flink’s ExpressionReducer： https://github.com/apache/flink/blob/master/flink-libraries/flink-table/src/main/scala/org/apache/flink/table/codegen/Expressi

Re: Switch to Scala 2.11 as a default build profile

+1. AWS EMR eco system is using Scala 2.11, and breaks with Scala 2.10. We had to build several Flink components (e.g. flink-kinesis-connector) ourselves in order to run on EMR. Defaulting to Scala 2.11 will greatly reduce adoption cost for Flink on EMR On Wed, Jun 28, 2017 at 9:34 AM, Till Rohr

[jira] [Created] (FLINK-7035) Flink Kinesis connector forces hard coding the AWS Region

Matt Pouttu-clarke created FLINK-7035: - Summary: Flink Kinesis connector forces hard coding the AWS Region Key: FLINK-7035 URL: https://issues.apache.org/jira/browse/FLINK-7035 Project: Flink

[jira] [Created] (FLINK-7034) GraphiteReporter cannot recover from lost connection

Aleksandr created FLINK-7034: Summary: GraphiteReporter cannot recover from lost connection Key: FLINK-7034 URL: https://issues.apache.org/jira/browse/FLINK-7034 Project: Flink Issue Type: Bug

[GitHub] flink-shaded pull request #5: [FLINK-7026] Add flink-shaded-asm-5 module

Github user asfgit closed the pull request at: https://github.com/apache/flink-shaded/pull/5 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Created] (FLINK-7033) Update Flink's MapR documentation to include default trust store for secure servers

Aniket created FLINK-7033: - Summary: Update Flink's MapR documentation to include default trust store for secure servers Key: FLINK-7033 URL: https://issues.apache.org/jira/browse/FLINK-7033 Project: Flink

[jira] [Created] (FLINK-7032) Intellij is constantly changing language level of sub projects back to 1.6

Piotr Nowojski created FLINK-7032: - Summary: Intellij is constantly changing language level of sub projects back to 1.6 Key: FLINK-7032 URL: https://issues.apache.org/jira/browse/FLINK-7032 Project:

[jira] [Created] (FLINK-7031) Document Gelly examples

Greg Hogan created FLINK-7031: - Summary: Document Gelly examples Key: FLINK-7031 URL: https://issues.apache.org/jira/browse/FLINK-7031 Project: Flink Issue Type: New Feature Components:

Re: Switch to Scala 2.11 as a default build profile

I'm +1 for changing the profile and to start a discussion to drop Scala 2.10. Scala 2.10 is already quite old and the current stable version is 2.12. I would be surprised to see many people still using Scala 2.10. Cheers, Till On Wed, Jun 28, 2017 at 4:53 PM, Ted Yu wrote: > Here is the KIP th

[GitHub] flink-shaded issue #5: [FLINK-7026] Add flink-shaded-asm-5 module

Github user rmetzger commented on the issue: https://github.com/apache/flink-shaded/pull/5 +1 to merge --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or i

Re: Switch to Scala 2.11 as a default build profile

Here is the KIP that drops support for Scala 2.10 in Kafka 0.11 : https://cwiki.apache.org/confluence/display/KAFKA/KIP-119%3A+Drop+Support+for+Scala+2.10+in+Kafka+0.11 FYI On Wed, Jun 28, 2017 at 7:23 AM, Piotr Nowojski wrote: > Yes, I know and I’m proposing to change this in parent pom by de

Re: Switch to Scala 2.11 as a default build profile

Yes, I know and I’m proposing to change this in parent pom by default to scala-2.11. Changing parent pom every time anyone wants to touch/build in Intellij Kafka 0.11 connector is not a great idea. This would require a developer to constantly stash those changes or commit and revert them before

Re: Switch to Scala 2.11 as a default build profile

You don't need to use the build profile in IntelliJ, just change scala.version and scala.binary.version in the parent pom (recent refactorings made this possible without changing every pom). What is the benefit for changing the default without dropping older versions when contributions are still l

Re: Switch to Scala 2.11 as a default build profile

I have created an issue for this: https://issues.apache.org/jira/browse/FLINK-7030 and PR: https://github.com/apache/flink/pull/4209 Piotrek > On Jun 28, 2017, at 2:45 PM, Aljoscha Krettek wrote:

[jira] [Created] (FLINK-7030) Build with scala-2.11 by default

Piotr Nowojski created FLINK-7030: - Summary: Build with scala-2.11 by default Key: FLINK-7030 URL: https://issues.apache.org/jira/browse/FLINK-7030 Project: Flink Issue Type: Improvement

Re: [DISCUSS] FLIP-21 - Improve object Copying/Reuse Mode for Streaming Runtime

+1 for changing the default if so many people encountered problems with serialisation costs. The first two modes don’t require any code changes, correct? Only the last one would require changes to the stream input processors. We should also keep this issue in mind: https://issues.apache.org/ji

Re: Switch to Scala 2.11 as a default build profile

+1 For changing the default. I think a lot of systems don’t even support 2.10 anymore. > On 28. Jun 2017, at 14:38, Ted Yu wrote: > > +1 on using Scale 2.11 as default. > Original message From: Piotr Nowojski > Date: 6/28/17 5:36 AM (GMT-08:00) To: > dev@flink.apache.org

Re: Switch to Scala 2.11 as a default build profile

+1 on using Scale 2.11 as default.  Original message From: Piotr Nowojski Date: 6/28/17 5:36 AM (GMT-08:00) To: dev@flink.apache.org Subject: Switch to Scala 2.11 as a default build profile Hi, I propose to switch to Scala 2.11 as a default and to have a Scala 2.10 build pr

Switch to Scala 2.11 as a default build profile

Hi, I propose to switch to Scala 2.11 as a default and to have a Scala 2.10 build profile. Now it is other way around. The reason for that is poor support for build profiles in Intellij, I was unable to make it work after I added Kafka 0.11 dependency (Kafka 0.11 dropped support for Scala 2.10)

[GitHub] flink-shaded pull request #5: [FLINK-7026] Add flink-shaded-asm-5 module

GitHub user zentol opened a pull request: https://github.com/apache/flink-shaded/pull/5 [FLINK-7026] Add flink-shaded-asm-5 module You can merge this pull request into a Git repository by running: $ git pull https://github.com/zentol/flink-shaded 7026 Alternatively you can re

[jira] [Created] (FLINK-7029) Documentation for WindowFunction is confusing

Felix Neutatz created FLINK-7029: Summary: Documentation for WindowFunction is confusing Key: FLINK-7029 URL: https://issues.apache.org/jira/browse/FLINK-7029 Project: Flink Issue Type: Impro

[jira] [Created] (FLINK-7028) Replace asm dependencies

Chesnay Schepler created FLINK-7028: --- Summary: Replace asm dependencies Key: FLINK-7028 URL: https://issues.apache.org/jira/browse/FLINK-7028 Project: Flink Issue Type: Sub-task C

[jira] [Created] (FLINK-7027) Replace netty dependencies

Chesnay Schepler created FLINK-7027: --- Summary: Replace netty dependencies Key: FLINK-7027 URL: https://issues.apache.org/jira/browse/FLINK-7027 Project: Flink Issue Type: Sub-task

[jira] [Created] (FLINK-7026) Add shaded asm dependency

Chesnay Schepler created FLINK-7026: --- Summary: Add shaded asm dependency Key: FLINK-7026 URL: https://issues.apache.org/jira/browse/FLINK-7026 Project: Flink Issue Type: Sub-task

Re: [DISCUSS] Backwards compatibility policy.

I haven't closely followed the discussion so far, but isn't it Apache policy that major versions should stay backwards compatible to all previous releases with the same major version? -s 2017-06-28 12:26 GMT+02:00 Kostas Kloudas : > I agree that 1.1 compatibility is the most important “pain poin

Re: [DISCUSS] Backwards compatibility policy.

I agree that 1.1 compatibility is the most important “pain point", as compatibility with the rest of the versions follows a more “systematic” approach. I think that discarding compatibility with 1.1 will clear some parts of the codebase significantly. Kostas > On Jun 27, 2017, at 6:03 PM, Ste

[GitHub] flink-shaded pull request #3: [FLINK-7007] Add README.md

Github user asfgit closed the pull request at: https://github.com/apache/flink-shaded/pull/3 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] flink-shaded pull request #4: Add flink-shaded-netty module

Github user asfgit closed the pull request at: https://github.com/apache/flink-shaded/pull/4 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is