[GitHub] flink pull request #2870: [FLINK-4565] Support for SQL IN operator

Github user NickolayVasilishin closed the pull request at: https://github.com/apache/flink/pull/2870 --- 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

[GitHub] flink issue #2870: [FLINK-4565] Support for SQL IN operator

Github user NickolayVasilishin commented on the issue: https://github.com/apache/flink/pull/2870 Hi, @twalthr I'm afraid I'm busy now with another project, so the task is now pending until Alexander Chermenin will continue working on it with my possible assistance

[GitHub] flink pull request #3040: [FLINK-3850] Add forward field annotations to Data...

GitHub user NickolayVasilishin opened a pull request: https://github.com/apache/flink/pull/3040 [FLINK-3850] Add forward field annotations to DataSet Add forward field annotations to DataSet operators generated by the Table API - Added field forwarding at most

[GitHub] flink issue #2870: [FLINK-4565] Support for SQL IN operator

Github user NickolayVasilishin commented on the issue: https://github.com/apache/flink/pull/2870 Also the last commit represents possible way of implementing subquery IN operator. On one hand, it's really simple implementation, all work delegates to already proprely working

[GitHub] flink issue #2870: [FLINK-4565] Support for SQL IN operator

Github user NickolayVasilishin commented on the issue: https://github.com/apache/flink/pull/2870 I've fixed all things above. Though, I've faced some problems while moving to another test base. It uses testing expressions directly in SELECT query, so I had to add new case

[GitHub] flink issue #2870: [FLINK-4565] Support for SQL IN operator

Github user NickolayVasilishin commented on the issue: https://github.com/apache/flink/pull/2870 Hi, @fhueske. I will update PR with fixed version soon. But I have a question. Is deduplication at In#toRexNode really needed since we are going to use hashset anyway? It's

[GitHub] flink pull request #2870: [FLINK-4565] Support for SQL IN operator

GitHub user NickolayVasilishin opened a pull request: https://github.com/apache/flink/pull/2870 [FLINK-4565] Support for SQL IN operator [FLINK-4565] Support for SQL IN operator This PR is a part of work on SQL IN operator in Table API, which implements IN for literals

[GitHub] flink pull request #2868: [FLINK-4565] Support for SQL IN operator

Github user NickolayVasilishin closed the pull request at: https://github.com/apache/flink/pull/2868 --- 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

[GitHub] flink pull request #2868: [FLINK-4565] Support for SQL IN operator

GitHub user NickolayVasilishin opened a pull request: https://github.com/apache/flink/pull/2868 [FLINK-4565] Support for SQL IN operator This PR is a part of work on SQL IN operator in Table API, which implements IN for literals. Two cases are covered: less and great then 20