Re: [VOTE] FLIP-238: Introduce FLIP-27-based Data Generator Source
Thanks Alexander for driving this FLIP! +1 (binding) Best regards, Qingsheng > On Jul 20, 2022, at 03:31, Alexander Fedulov wrote: > > Hi everyone, > > following the discussion in [1], I would like to open up a vote for > adding a FLIP-27-based Data Generator Source [2]. > > The addition of this source also unblocks the currently pending > efforts for deprecating the Source Function API [3]. > > The poll will be open until July 25 (72h + weekend), unless there is > an objection or not enough votes. > > [1] https://lists.apache.org/thread/7gjxto1rmkpff4kl54j8nlg5db2rqhkt > [2] https://cwiki.apache.org/confluence/x/9Av1D > [3] https://github.com/apache/flink/pull/20049#issuecomment-1170948767 > > Best, > Alexander Fedulov
[jira] [Created] (FLINK-28754) document that Java 8 is required to build table store
David Anderson created FLINK-28754: -- Summary: document that Java 8 is required to build table store Key: FLINK-28754 URL: https://issues.apache.org/jira/browse/FLINK-28754 Project: Flink Issue Type: Improvement Components: Documentation, Table Store Reporter: David Anderson The table store can not be built with Java 11, but the "build from source" instructions don't mention this restriction. https://nightlies.apache.org/flink/flink-table-store-docs-master/docs/engines/build/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-28753) Improve FilterIntoJoinRule which could push some predicate to another side
godfrey he created FLINK-28753: -- Summary: Improve FilterIntoJoinRule which could push some predicate to another side Key: FLINK-28753 URL: https://issues.apache.org/jira/browse/FLINK-28753 Project: Flink Issue Type: Improvement Components: Table SQL / Planner Reporter: godfrey he Fix For: 1.16.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-28752) Add the json plan support in Python UDFs
Huang Xingbo created FLINK-28752: Summary: Add the json plan support in Python UDFs Key: FLINK-28752 URL: https://issues.apache.org/jira/browse/FLINK-28752 Project: Flink Issue Type: New Feature Components: API / Python Affects Versions: 1.16.0 Reporter: Huang Xingbo Assignee: Huang Xingbo Fix For: 1.16.0 In release-1.15, we removed the json plan support in https://issues.apache.org/jira/browse/FLINK-26060. Since we have updated PyFlink to use the new type system in https://issues.apache.org/jira/browse/FLINK-25231, we need to add the json plan support again. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-28751) Poor performance of the built in json_value function
Aitozi created FLINK-28751: -- Summary: Poor performance of the built in json_value function Key: FLINK-28751 URL: https://issues.apache.org/jira/browse/FLINK-28751 Project: Flink Issue Type: Improvement Components: Table SQL / Runtime Reporter: Aitozi Attachments: image-2022-07-30-15-47-34-788.png When I use the JSON_VALUE function, I found the performance is very poor. It's mainly affected by the heavy lock operation in jsonpath inner LRUCache which is also observed by other systems, eg: [https://github.com/apache/pinot/pull/7409|https://github.com/apache/pinot/pull/7409*] !image-2022-07-30-15-47-34-788.png|width=2346,height=996! So I purpose to use a different cache to replace the current one for better performance. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FLINK-28750) Whether to add comment for hive table
hehuiyuan created FLINK-28750:
-
Summary: Whether to add comment for hive table
Key: FLINK-28750
URL: https://issues.apache.org/jira/browse/FLINK-28750
Project: Flink
Issue Type: Improvement
Reporter: hehuiyuan
Currently, I have a hive ddl，as follows
{code:java}
"set table.sql-dialect=hive;\n" +
"CREATE TABLE IF NOT EXISTS myhive.dev.shipu3_test_1125 (\n" +
" `id` int COMMENT 'ia',\n" +
" `cartdid` bigint COMMENT 'aaa',\n" +
" `customer` string COMMENT '',\n" +
" `product` string COMMENT '',\n" +
" `price` double COMMENT '',\n" +
" `dt` STRING COMMENT ''\n" +
") PARTITIONED BY (dt STRING) STORED AS TEXTFILE TBLPROPERTIES (\n" +
" 'streaming-source.enable' = 'false',\n" +
" 'streaming-source.partition.include' = 'all',\n" +
" 'lookup.join.cache.ttl' = '12 h'\n" +
")"; {code}
It is parsed as SqlCreateHiveTable by hive dialect parser. But the field commet
is lost.
!image-2022-07-30-15-21-58-062.png|width=568,height=283!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (FLINK-28749) Add resource type to KubernetesResourceNamespaceMetricGroup scope
Gyula Fora created FLINK-28749: -- Summary: Add resource type to KubernetesResourceNamespaceMetricGroup scope Key: FLINK-28749 URL: https://issues.apache.org/jira/browse/FLINK-28749 Project: Flink Issue Type: Improvement Components: Kubernetes Operator Reporter: Gyula Fora Assignee: Gyula Fora Fix For: kubernetes-operator-1.2.0 Currently the KubernetesResourceMetricGroup and KubernetesResourceNamespaceMetricGroup doesn't have information about the resource type and different metrics add this differently. We should unify this and always have the managed resource type FlinkDeployment/FlinkSessionJob in the scope. -- This message was sent by Atlassian Jira (v8.20.10#820010)
