[jira] [Commented] (FLINK-3097) Add support for custom functions in Table API
[
https://issues.apache.org/jira/browse/FLINK-3097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15124856#comment-15124856
]
ASF GitHub Bot commented on FLINK-3097:
---
Github user twalthr closed the pull request at:
https://github.com/apache/flink/pull/1429
> 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 Feature
> Components: Table API
>Reporter: Timo Walther
>Assignee: Timo Walther
>
> Currently, the Table API has a very limited set of built-in functions.
> Support for custom functions can solve this problem. Adding of a custom row
> function could look like:
> {code}
> TableEnvironment tableEnv = new TableEnvironment();
> RowFunction rf = new RowFunction() {
> @Override
> public String call(Object[] args) {
> return ((String) args[0]).trim();
> }
> };
> tableEnv.getConfig().registerRowFunction("TRIM", rf,
> BasicTypeInfo.STRING_TYPE_INFO);
> DataSource input = env.fromElements(
> new Tuple1<>(" 1 "));
> Table table = tableEnv.fromDataSet(input);
> Table result = table.select("TRIM(f0)");
> {code}
> This feature is also necessary as part of FLINK-2099.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] flink pull request: [FLINK-3097] [table] Add support for custom fu...
Github user twalthr commented on the pull request: https://github.com/apache/flink/pull/1429#issuecomment-177156151 I'm currently preparing it for the `tableOnCalcite` branch. I will close this PR. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] flink pull request: [FLINK-3097] [table] Add support for custom fu...
Github user twalthr closed the pull request at: https://github.com/apache/flink/pull/1429 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (FLINK-3097) Add support for custom functions in Table API
[
https://issues.apache.org/jira/browse/FLINK-3097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15124855#comment-15124855
]
ASF GitHub Bot commented on FLINK-3097:
---
Github user twalthr commented on the pull request:
https://github.com/apache/flink/pull/1429#issuecomment-177156151
I'm currently preparing it for the `tableOnCalcite` branch. I will close
this PR.
> 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 Feature
> Components: Table API
>Reporter: Timo Walther
>Assignee: Timo Walther
>
> Currently, the Table API has a very limited set of built-in functions.
> Support for custom functions can solve this problem. Adding of a custom row
> function could look like:
> {code}
> TableEnvironment tableEnv = new TableEnvironment();
> RowFunction rf = new RowFunction() {
> @Override
> public String call(Object[] args) {
> return ((String) args[0]).trim();
> }
> };
> tableEnv.getConfig().registerRowFunction("TRIM", rf,
> BasicTypeInfo.STRING_TYPE_INFO);
> DataSource input = env.fromElements(
> new Tuple1<>(" 1 "));
> Table table = tableEnv.fromDataSet(input);
> Table result = table.select("TRIM(f0)");
> {code}
> This feature is also necessary as part of FLINK-2099.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] flink pull request: [FLINK-2237] [runtime] Add hash-based combiner...
Github user fhueske commented on the pull request: https://github.com/apache/flink/pull/1517#issuecomment-177204208 I agree with @mbalassi. Adding a strategy hint to the API, similar to the join hints for inner and outer joins is a good idea. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (FLINK-2237) Add hash-based Aggregation
[ https://issues.apache.org/jira/browse/FLINK-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15124928#comment-15124928 ] ASF GitHub Bot commented on FLINK-2237: --- Github user fhueske commented on the pull request: https://github.com/apache/flink/pull/1517#issuecomment-177204208 I agree with @mbalassi. Adding a strategy hint to the API, similar to the join hints for inner and outer joins is a good idea. > Add hash-based Aggregation > -- > > Key: FLINK-2237 > URL: https://issues.apache.org/jira/browse/FLINK-2237 > Project: Flink > Issue Type: New Feature >Reporter: Rafiullah Momand >Assignee: Gabor Gevay >Priority: Minor > > Aggregation functions at the moment are implemented in a sort-based way. > How can we implement hash based Aggregation for Flink? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FLINK-2870) Add support for accumulating/discarding for Event-Time Windows
[ https://issues.apache.org/jira/browse/FLINK-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15125217#comment-15125217 ] Shikhar Bhushan commented on FLINK-2870: What is the current behaviour if a late element arrives and what kind of customization is possible? > Add support for accumulating/discarding for Event-Time Windows > -- > > Key: FLINK-2870 > URL: https://issues.apache.org/jira/browse/FLINK-2870 > Project: Flink > Issue Type: Sub-task > Components: Streaming >Reporter: Aljoscha Krettek >Assignee: Aljoscha Krettek > > This would allow to specify whether windows should be discarded after the > trigger fires or kept in the operator if late elements arrive. > When keeping elements, the user would also have to specify an allowed > lateness time after which the window contents are discarded without emitting > any further window evaluation result. > If elements arrive after the allowed lateness they would trigger the window > immediately with only the one single element. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
