[jira] [Created] (FLINK-3837) Create FLOOR/CEIL function

Timo Walther created FLINK-3837: --- Summary: Create FLOOR/CEIL function Key: FLINK-3837 URL: https://issues.apache.org/jira/browse/FLINK-3837 Project: Flink Issue Type: Sub-task

[jira] [Created] (FLINK-3786) Add BigDecimal and BigInteger as Basic types

Timo Walther created FLINK-3786: --- Summary: Add BigDecimal and BigInteger as Basic types Key: FLINK-3786 URL: https://issues.apache.org/jira/browse/FLINK-3786 Project: Flink Issue Type: New

[jira] [Created] (FLINK-3749) Improve decimal handling

Timo Walther created FLINK-3749: --- Summary: Improve decimal handling Key: FLINK-3749 URL: https://issues.apache.org/jira/browse/FLINK-3749 Project: Flink Issue Type: Bug Components

[jira] [Created] (FLINK-3748) Add CASE function to Table API

Timo Walther created FLINK-3748: --- Summary: Add CASE function to Table API Key: FLINK-3748 URL: https://issues.apache.org/jira/browse/FLINK-3748 Project: Flink Issue Type: Sub-task

Re: Table API / SQL Queries and Code Generation

Hi Gábor, the code generation in the Table API is in a very early stage and contains not much optimization logic so far. Currently we extend the functionality to support the most important SQL operations. It will need some time until we can further optimize the generated code (e.g. for

[jira] [Created] (FLINK-3580) Reintroduce Date/Time and implement scalar functions for it

Timo Walther created FLINK-3580: --- Summary: Reintroduce Date/Time and implement scalar functions for it Key: FLINK-3580 URL: https://issues.apache.org/jira/browse/FLINK-3580 Project: Flink

[jira] [Created] (FLINK-3579) Improve String concatenation

Timo Walther created FLINK-3579: --- Summary: Improve String concatenation Key: FLINK-3579 URL: https://issues.apache.org/jira/browse/FLINK-3579 Project: Flink Issue Type: Bug

[jira] [Created] (FLINK-3574) Implement math functions for Table API

Timo Walther created FLINK-3574: --- Summary: Implement math functions for Table API Key: FLINK-3574 URL: https://issues.apache.org/jira/browse/FLINK-3574 Project: Flink Issue Type: Sub-task

[jira] [Created] (FLINK-3573) Implement more String functions for Table API

Timo Walther created FLINK-3573: --- Summary: Implement more String functions for Table API Key: FLINK-3573 URL: https://issues.apache.org/jira/browse/FLINK-3573 Project: Flink Issue Type: Sub

[jira] [Created] (FLINK-3567) Rework selection when grouping in Table API

Timo Walther created FLINK-3567: --- Summary: Rework selection when grouping in Table API Key: FLINK-3567 URL: https://issues.apache.org/jira/browse/FLINK-3567 Project: Flink Issue Type: Bug

Re: Input type validation is killing me

Can you open an issue with an example of your custom TypeInfo? I will then open a suitable PR for it. On 02.03.2016 15:33, Gyula Fóra wrote: Would that work with generic classes? Timo Walther <twal...@apache.org> ezt írta (időpont: 2016. márc. 2., Sze, 15:22): After thinking about

Re: Input type validation is killing me

:00, Gyula Fóra wrote: Hi! Yes I think, that sounds good :) We just need to make sure that this works with things like the TupleTypeInfo which is built-on but I can still mix in new Types for the fields. Thanks, Gyula Timo Walther <twal...@apache.org> ezt írta (időpont: 2016. márc. 2., S

[jira] [Created] (FLINK-3564) Implement distinct() for Table API

Timo Walther created FLINK-3564: --- Summary: Implement distinct() for Table API Key: FLINK-3564 URL: https://issues.apache.org/jira/browse/FLINK-3564 Project: Flink Issue Type: New Feature

[jira] [Created] (FLINK-3498) Implement TRIM, SUBSTRING as reference design for Table API

Timo Walther created FLINK-3498: --- Summary: Implement TRIM, SUBSTRING as reference design for Table API Key: FLINK-3498 URL: https://issues.apache.org/jira/browse/FLINK-3498 Project: Flink

[jira] [Created] (FLINK-3497) Add SQL scalar functions to Table API

Timo Walther created FLINK-3497: --- Summary: Add SQL scalar functions to Table API Key: FLINK-3497 URL: https://issues.apache.org/jira/browse/FLINK-3497 Project: Flink Issue Type: New Feature

[jira] [Created] (FLINK-3489) Refactor Table API before merging into master

Timo Walther created FLINK-3489: --- Summary: Refactor Table API before merging into master Key: FLINK-3489 URL: https://issues.apache.org/jira/browse/FLINK-3489 Project: Flink Issue Type: Sub

[jira] [Created] (FLINK-3152) Support all comparisons for Date type

Timo Walther created FLINK-3152: --- Summary: Support all comparisons for Date type Key: FLINK-3152 URL: https://issues.apache.org/jira/browse/FLINK-3152 Project: Flink Issue Type: Improvement

[jira] [Created] (FLINK-3153) Support all comparisons for String type

Timo Walther created FLINK-3153: --- Summary: Support all comparisons for String type Key: FLINK-3153 URL: https://issues.apache.org/jira/browse/FLINK-3153 Project: Flink Issue Type: Improvement

[jira] [Created] (FLINK-3097) Add support for custom functions in Table API

Timo Walther created FLINK-3097: --- Summary: Add support for custom functions in Table API Key: FLINK-3097 URL: https://issues.apache.org/jira/browse/FLINK-3097 Project: Flink Issue Type: New

Re: Either not NotSerializableException and InvalidTypesException

Hi Vasia, regarding your TypeExtractor problem. The TypeExtractor works correctly. The with() function of the JoinOperator calls the wrong TypeExtractor method that does not allow missing type info. This is a bug. Can open an issue for that? Regards, Timo On 28.11.2015 20:18, Vasiliki

[jira] [Created] (FLINK-3086) ExpressionParser does not support concatenation of suffix operations

Timo Walther created FLINK-3086: --- Summary: ExpressionParser does not support concatenation of suffix operations Key: FLINK-3086 URL: https://issues.apache.org/jira/browse/FLINK-3086 Project: Flink

Re: The null in Flink

Hi Chengxiang, I totally agree that the Table API should fully support NULL values. The Table API is a logical API and therefore we should be as close to ANSI SQL as possible. Rows need to be nullable in the near future. 2. i, ii, iii and iv sound reasonable. But v, vi and vii sound to much

[jira] [Created] (FLINK-3068) Add a Table API configuration to TableEnvironment

Timo Walther created FLINK-3068: --- Summary: Add a Table API configuration to TableEnvironment Key: FLINK-3068 URL: https://issues.apache.org/jira/browse/FLINK-3068 Project: Flink Issue Type

Re: withParameters() for Streaming API

. Sax wrote: We had this discussion a while ago. If I recall correctly, "withParameters()" is not encourage to be used in DataSet either. This is the thread: https://mail-archives.apache.org/mod_mbox/flink-dev/201509.mbox/%3C55EC69CD.1070003%40apache.org%3E -Matthias On 11/24/2015 02:1

withParameters() for Streaming API

Hi all, I want to set the Configuration of a streaming operator and access it via the open method of the RichFunction. There is no possibility to set the Configuration of the open method at the moment, right? Can I open an issue for a withParameters() equivalent for the Stremaing API?

[jira] [Created] (FLINK-3060) Add possibility to integrate custom types into the TypeExtractor

Timo Walther created FLINK-3060: --- Summary: Add possibility to integrate custom types into the TypeExtractor Key: FLINK-3060 URL: https://issues.apache.org/jira/browse/FLINK-3060 Project: Flink

Re: [DISCUSSION] Type hints versus TypeInfoParser

. (Not sure if all that is implemented in the TypeExtractor, though). What do you think? Stephan On Wed, Nov 18, 2015 at 6:03 PM, Timo Walther <twal...@apache.org> wrote: If the TypeExtractor is not able to handle the fields of a Pojo correctly, the String parser is quite useful to say "org.my.Pojo

Re: Add BigDecimal and BigInteger as types

. They are currently generic types and handled by Kryo, which has (AFAIK) proper serializers for them. Are there more benefits of native support (other than more compact serialization) that you are thinking of? On Wed, Nov 18, 2015 at 5:55 PM, Timo Walther <twal...@apache.org> wrote: Hey everyone

Add BigDecimal and BigInteger as types

Hey everyone, I'm not sure if we already had a discussion about it but as we are currently adding new types like the Either type, I would like to discuss it again. I think especially for business or scientific applications it makes sense to support the BigInteger and BigDecimal types

Re: [DISCUSSION] Type hints versus TypeInfoParser

If the TypeExtractor is not able to handle the fields of a Pojo correctly, the String parser is quite useful to say

Re: Error in during TypeExtraction

This looks like a bug. Can you open an issue for that? I will look into it later. Regards, Timo On 12.11.2015 13:16, Gyula Fóra wrote: Hey, I get a weird error when I try to execute my job on the cluster. Locally this works fine but running it from the command line fails during

Re: [DISCUSSION] Type hints versus TypeInfoParser

owerful and type safe than the String/Parser way of giving hints, I was wondering whether we should add this and deprecate the String variant. If we do that, 1.0 is the time to do that. What do you think about this idea? @Timo Walther Since you worked a lot on types/parser/etc - what is your

Re: Function input type validation

The reason for input validation is to check if the Function is fully compatible. Actually only the return types are necessary, but it prohibits stupid implementation mistakes and undesired behavior. E.g. if you implement a "class MyMapper extends MapFunction{}" and use it for

[jira] [Created] (FLINK-2985) Allow different field names for unionAll() in Table API

Timo Walther created FLINK-2985: --- Summary: Allow different field names for unionAll() in Table API Key: FLINK-2985 URL: https://issues.apache.org/jira/browse/FLINK-2985 Project: Flink Issue

[jira] [Created] (FLINK-2961) Add support for basic type Date in Table API

Timo Walther created FLINK-2961: --- Summary: Add support for basic type Date in Table API Key: FLINK-2961 URL: https://issues.apache.org/jira/browse/FLINK-2961 Project: Flink Issue Type

Re: Powered by Flink

+1 for adding it to the website instead of wiki. "Who is using Flink?" is always a question difficult to answer to interested users. On 19.10.2015 15:08, Suneel Marthi wrote: +1 to this. On Mon, Oct 19, 2015 at 3:00 PM, Fabian Hueske > wrote:

Re: Powered by Flink

Ah ok, sorry. I think linking to the wiki is also ok. On 19.10.2015 15:18, Fabian Hueske wrote: @Timo: The proposal was to keep the list in the wiki (can be easily extended) but link from the main website to the wiki page. 2015-10-19 15:16 GMT+02:00 Timo Walther <twal...@apache.org>

[jira] [Created] (FLINK-2828) Add interfaces for Table API input formats

Timo Walther created FLINK-2828: --- Summary: Add interfaces for Table API input formats Key: FLINK-2828 URL: https://issues.apache.org/jira/browse/FLINK-2828 Project: Flink Issue Type: New

Re: [ANNOUNCE] Welcome Matthias Sax as new committer

Congratulations Matthias! Regards, Timo On 02.09.2015 13:32, Chiwan Park wrote: Welcome Matthias! :) Regards, Chiwan Park On Sep 2, 2015, at 8:30 PM, Kostas Tzoumas wrote: The Project Management Committee (PMC) of Apache Flink has asked Matthias Sax to become a

[jira] [Created] (FLINK-2410) PojoTypeInfo is not completely serializable

Timo Walther created FLINK-2410: --- Summary: PojoTypeInfo is not completely serializable Key: FLINK-2410 URL: https://issues.apache.org/jira/browse/FLINK-2410 Project: Flink Issue Type: Bug

[jira] [Created] (FLINK-2316) Optimize the SCA for bytecode generated by Scala

Timo Walther created FLINK-2316: --- Summary: Optimize the SCA for bytecode generated by Scala Key: FLINK-2316 URL: https://issues.apache.org/jira/browse/FLINK-2316 Project: Flink Issue Type

Re: SQL on Flink

this. Since the Table API is still a fairly new component and not very feature rich, it might make sense to extend and strengthen it before putting something major on top. Cheers, Fabian 2015-05-26 21:38 GMT+02:00 Timo Walther twal...@apache.org: Hey everyone, I would be interested in having

Re: New project website

I completely agree with Robert. Less marketing, more technical information targeted to the user group. I think the diagram could be a little bit larger and the blog post smaller, so that the lines meet in the middle ;) On 11.05.2015 14:39, Robert Metzger wrote: I think its fine when the

Re: Merge Python API

+1 On 20.04.2015 14:49, Gyula Fóra wrote: +1 On Mon, Apr 20, 2015 at 2:41 PM, Fabian Hueske fhue...@gmail.com wrote: +1 2015-04-20 14:39 GMT+02:00 Maximilian Michels m...@apache.org: +1 Let's merge it to flink-staging and get some people to use it. On Mon, Apr 20, 2015 at 2:21 PM, Kostas

Re: About Operator and OperatorBase

I share Stephans opinion. By the way, we could also find a common name for operators with two inputs. Sometimes it's TwoInputXXX, DualInputXXX, BinaryInputXXX... pretty inconsistent. On 15.04.2015 17:48, Till Rohrmann wrote: I would also be in favour of making the distinction between the

[jira] [Created] (FLINK-1900) Table API documentation example does not work

Timo Walther created FLINK-1900: --- Summary: Table API documentation example does not work Key: FLINK-1900 URL: https://issues.apache.org/jira/browse/FLINK-1900 Project: Flink Issue Type: Bug

Re: [VOTE] Name of Expression API Representation

+Table API Same thoughts as Stephan. Table is more common in the economy than Relation. On 25.03.2015 21:30, Stephan Ewen wrote: +Table API / Table I have a feeling that Relation is a name mostly used by people with a deeper background in (relational) databases, while table is more the

Re: [DISCUSS] Make a release to be announced at ApacheCon

+1 for a beta release. So there is no feature-freeze until the RC right? On 26.03.2015 15:32, Márton Balassi wrote: +1 for the early release. I'd call it 0.9-milestone1. On Thu, Mar 26, 2015 at 1:37 PM, Maximilian Michels m...@apache.org wrote: +1 for a beta release: 0.9-beta. On Thu, Mar

[jira] [Created] (FLINK-1777) Update Java 8 Lambdas with Eclipse documentation

Timo Walther created FLINK-1777: --- Summary: Update Java 8 Lambdas with Eclipse documentation Key: FLINK-1777 URL: https://issues.apache.org/jira/browse/FLINK-1777 Project: Flink Issue Type: Bug

Semantic Properties and Functions with Iterables

Hey all, I'm currently working a lot on the UDF static code analyzer. But I have a general question about Semantic Properties which might be also interesting for other users. How is the ForwardedFields annotation interpreted for UDF functions with Iterables? An example can be found in:

Re: Eclipse JDT, Java 8, lambdas

... On 09.02.2015 16:28, Stephan Ewen wrote: Is it possible to use this compiler for the java 8 quickstart archetypes? On Mon, Feb 9, 2015 at 4:14 PM, Timo Walther twal...@apache.org wrote: The fix is included in 4.4.2. However, it seems that even if the compiler option

Re: kryoException : Buffer underflow

Hey Nam-Luc, I think your problem lies in the following line: .returns(eu.euranova.flink.Centroid25) If you do not specify the fields of the class in the String by using myfield=String,otherField=int, the underlying parser will create an GenericTypeInfo type information which then uses Kryo

Re: Eclipse JDT, Java 8, lambdas

Hey, it seems that 4.4.2 also includes the fix (https://projects.eclipse.org/projects/eclipse/releases/4.4.2/bugs) and will be released end of february. I will try Eclipse Luna SR2 RC2 today and check if it is working. Regards, Timo On 09.02.2015 10:05, Nam-Luc Tran wrote: I did try the

Re: Sorting of fields

Ok, I found an earlier discussion about it. Sorry for the mail. However, I think this is a very important feature and I should be added soon. On 04.02.2015 14:38, Timo Walther wrote: Hey, is it correct that we currently do not support sorting without any grouping? I had this question by 2

Re: Fwd: TypeSerializerInputFormat cannot determine its type automatically

Hey Alexander, I have looked into your issue. You can simply use env.createInput(InputFormat,TypeInformation) instead of env.readFile() then you can pass TypeInformation manually without implementing ResultTypeQueryable. Regards, Timo On 29.01.2015 14:54, Alexander Alexandrov wrote: The

<    9   10   11   12   13   14