[jira] [Created] (FLINK-24914) Support implicit type conversion in SQL like "select int_field = varchar_field"

xuyang created FLINK-24914: -- Summary: Support implicit type conversion in SQL like "select int_field = varchar_field" Key: FLINK-24914 URL: https://issues.apache.org/jira/browse/FLINK-24914 Project: Flink

[jira] [Commented] (FLINK-24914) Support implicit type conversion in SQL like "select int_field = varchar_field"

[ https://issues.apache.org/jira/browse/FLINK-24914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17444282#comment-17444282 ] xuyang commented on FLINK-24914: Hi, [~qingru zhang] . In a sense, it is, but FLIP-154 have not been

[jira] [Commented] (FLINK-24717) Push down partitions before filters

[ https://issues.apache.org/jira/browse/FLINK-24717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437100#comment-17437100 ] xuyang commented on FLINK-24717: I'll try to fix it. > Push down partitions before filters >

[jira] [Commented] (FLINK-24716) Non-equality predicates on partition columns lead to incorrect plans

[ https://issues.apache.org/jira/browse/FLINK-24716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437098#comment-17437098 ] xuyang commented on FLINK-24716: The plan seems correct, because the condition "d > '2012'" has been

[jira] [Created] (FLINK-24632) "where ... in(..)" has wrong result

xuyang created FLINK-24632: -- Summary: "where ... in(..)" has wrong result Key: FLINK-24632 URL: https://issues.apache.org/jira/browse/FLINK-24632 Project: Flink Issue Type: Bug

[jira] [Created] (FLINK-24835) "group by" in the interval join will throw a exception

xuyang created FLINK-24835: -- Summary: "group by" in the interval join will throw a exception Key: FLINK-24835 URL: https://issues.apache.org/jira/browse/FLINK-24835 Project: Flink Issue Type: Bug

[jira] [Created] (FLINK-24754) PushDownSepcs are better to be print by a clear order.

xuyang created FLINK-24754: -- Summary: PushDownSepcs are better to be print by a clear order. Key: FLINK-24754 URL: https://issues.apache.org/jira/browse/FLINK-24754 Project: Flink Issue Type:

[jira] [Commented] (FLINK-25475) When windowAgg and groupAgg are included at the same time, there is no assigner generated but MiniBatch optimization is still used.

[ https://issues.apache.org/jira/browse/FLINK-25475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17476968#comment-17476968 ] xuyang commented on FLINK-25475: Hi ,[~ChangjiGuo] . Are you glad to provide the test case to be

[jira] [Commented] (FLINK-25476) CharType lost in the creation of MaxAggFunction & MinAggFunction

[ https://issues.apache.org/jira/browse/FLINK-25476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17476949#comment-17476949 ] xuyang commented on FLINK-25476: I'll try to fix this issue. > CharType lost in the creation of

[jira] [Commented] (FLINK-26051) one sql has row_number =1 and the subsequent SQL has "case when" and "where" statement result Exception : The window can only be ordered in ASCENDING mode

[ https://issues.apache.org/jira/browse/FLINK-26051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17499312#comment-17499312 ] xuyang commented on FLINK-26051: Hi, thanks to report this bug! Would you like to fix this bug?

[jira] [Created] (FLINK-26975) TableTestBase will not generate exec node tree after generating rel node tree

xuyang created FLINK-26975: -- Summary: TableTestBase will not generate exec node tree after generating rel node tree Key: FLINK-26975 URL: https://issues.apache.org/jira/browse/FLINK-26975 Project: Flink

[jira] [Commented] (FLINK-26829) ClassCastException will be thrown when the second operand of divide is a function call

[ https://issues.apache.org/jira/browse/FLINK-26829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17511542#comment-17511542 ] xuyang commented on FLINK-26829: I'll try to fix it > ClassCastException will be thrown when the

[jira] [Created] (FLINK-27247) when add numeric casting rules, some logics are lost

xuyang created FLINK-27247: -- Summary: when add numeric casting rules, some logics are lost Key: FLINK-27247 URL: https://issues.apache.org/jira/browse/FLINK-27247 Project: Flink Issue Type: Bug

[jira] [Updated] (FLINK-27247) when add numeric casting rules, some logics are lost

[ https://issues.apache.org/jira/browse/FLINK-27247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuyang updated FLINK-27247: --- Description: Add the following test cases in ScalarFunctionsTest:   {code:java} // code placeholder @Test

[jira] [Updated] (FLINK-27247) when add numeric casting rules, some logics are lost

[ https://issues.apache.org/jira/browse/FLINK-27247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuyang updated FLINK-27247: --- Description: Add the following test cases in ScalarFunctionsTest: {code:java} // code placeholder @Test def

[jira] [Commented] (FLINK-27247) when add numeric casting rules, some logics are lost

[ https://issues.apache.org/jira/browse/FLINK-27247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17522146#comment-17522146 ] xuyang commented on FLINK-27247: I'll try to fix it > when add numeric casting rules, some logics are

[jira] [Updated] (FLINK-27247) CAST is not compatible with legacy behavior

[ https://issues.apache.org/jira/browse/FLINK-27247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuyang updated FLINK-27247: --- Summary: CAST is not compatible with legacy behavior (was: when add numeric casting rules, some logics are

[jira] [Updated] (FLINK-27247) ScalarOperatorGens.numericCasting is not compatible with legacy behavior

[ https://issues.apache.org/jira/browse/FLINK-27247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuyang updated FLINK-27247: --- Summary: ScalarOperatorGens.numericCasting is not compatible with legacy behavior (was: CAST is not

[jira] [Commented] (FLINK-27247) ScalarOperatorGens.numericCasting is not compatible with legacy behavior

[ https://issues.apache.org/jira/browse/FLINK-27247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17522626#comment-17522626 ] xuyang commented on FLINK-27247: Hi, [~matriv], I think currently this is not the problem with casting.

[jira] [Commented] (FLINK-33397) FLIP-373: Support Configuring Different State TTLs using SQL Hint

[ https://issues.apache.org/jira/browse/FLINK-33397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782453#comment-17782453 ] xuyang commented on FLINK-33397: Hi, [~qingyue] .I'd like to take this jira.  > FLIP-373: Support

[jira] [Commented] (FLINK-33217) Flink SQL: UNNEST fails with on LEFT JOIN with NOT NULL type in array

[ https://issues.apache.org/jira/browse/FLINK-33217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17781259#comment-17781259 ] xuyang commented on FLINK-33217: This issue is related to FLINK-31830. The node 'unnest' will be convert

[jira] [Commented] (FLINK-33372) Cryptic exception for a sub query in a CompiledPlan

[ https://issues.apache.org/jira/browse/FLINK-33372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17781280#comment-17781280 ] xuyang commented on FLINK-33372: Hi, [~dwysakowicz] . It seems related about CALCITE-4521. Since Calcite

[jira] [Created] (FLINK-33395) The join hint doesn't work when appears in subquery

xuyang created FLINK-33395: -- Summary: The join hint doesn't work when appears in subquery Key: FLINK-33395 URL: https://issues.apache.org/jira/browse/FLINK-33395 Project: Flink Issue Type: Bug

[jira] [Created] (FLINK-33396) The table alias when using join hints should be removed in the final plan

xuyang created FLINK-33396: -- Summary: The table alias when using join hints should be removed in the final plan Key: FLINK-33396 URL: https://issues.apache.org/jira/browse/FLINK-33396 Project: Flink

[jira] [Commented] (FLINK-33395) The join hint doesn't work when appears in subquery

[ https://issues.apache.org/jira/browse/FLINK-33395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17780916#comment-17780916 ] xuyang commented on FLINK-33395: The root case is that the join hint is not propagated inside the

[jira] [Updated] (FLINK-33396) The table alias should be removed in the final plan when using join hints

[ https://issues.apache.org/jira/browse/FLINK-33396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuyang updated FLINK-33396: --- Summary: The table alias should be removed in the final plan when using join hints (was: The table alias

[jira] [Updated] (FLINK-33396) The table alias when using join hints should be removed in the final plan

[ https://issues.apache.org/jira/browse/FLINK-33396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuyang updated FLINK-33396: --- Description: See the existent test 'NestLoopJoinHintTest#testJoinHintWithJoinHintInCorrelateAndWithAgg',

[jira] [Commented] (FLINK-33396) The table alias when using join hints should be removed in the final plan

[ https://issues.apache.org/jira/browse/FLINK-33396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17780919#comment-17780919 ] xuyang commented on FLINK-33396: The alias hints should be removed while visiting subquery. I'll try to

[jira] [Commented] (FLINK-33353) SQL fails because "TimestampType.kind" is not serialized

[ https://issues.apache.org/jira/browse/FLINK-33353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17779471#comment-17779471 ] xuyang commented on FLINK-33353: Hi, [~ferenc-csaky] . How can you serialize the tables, views and etc ?

[jira] [Commented] (FLINK-33200) ItemAt Expression validation fail in Table API due to type mismatch

[ https://issues.apache.org/jira/browse/FLINK-33200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17774295#comment-17774295 ] xuyang commented on FLINK-33200: Hi, [~andyglow] , maybe this flip[1] can be referred.

[jira] [Comment Edited] (FLINK-33200) ItemAt Expression validation fail in Table API due to type mismatch

[ https://issues.apache.org/jira/browse/FLINK-33200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17774295#comment-17774295 ] xuyang edited comment on FLINK-33200 at 10/12/23 2:19 AM: -- Hi, [~andyglow] ,

[jira] [Commented] (FLINK-33200) ItemAt Expression validation fail in Table API due to type mismatch

[ https://issues.apache.org/jira/browse/FLINK-33200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17774296#comment-17774296 ] xuyang commented on FLINK-33200: cc [~twalthr]  > ItemAt Expression validation fail in Table API due to

[jira] [Commented] (FLINK-33200) ItemAt Expression validation fail in Table API due to type mismatch

[ https://issues.apache.org/jira/browse/FLINK-33200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17773908#comment-17773908 ] xuyang commented on FLINK-33200: Hi, [~andyglow] . I think the issue 1 and 2 are caused by different

[jira] [Comment Edited] (FLINK-33200) ItemAt Expression validation fail in Table API due to type mismatch

[ https://issues.apache.org/jira/browse/FLINK-33200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17773908#comment-17773908 ] xuyang edited comment on FLINK-33200 at 10/11/23 6:06 AM: -- Hi, [~andyglow] . I

[jira] [Commented] (FLINK-33200) ItemAt Expression validation fail in Table API due to type mismatch

[ https://issues.apache.org/jira/browse/FLINK-33200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17773962#comment-17773962 ] xuyang commented on FLINK-33200: Hi, [~ZhenqiuHuang] , can you provide the code caused this issue?

[jira] [Commented] (FLINK-24024) Support session Window TVF

[ https://issues.apache.org/jira/browse/FLINK-24024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17773517#comment-17773517 ] xuyang commented on FLINK-24024: Hi, [~Sergey Nuyanzin] [~twalthr] ，I did a basic poc on my branch here

[jira] [Commented] (FLINK-20539) Type mismatch when using ROW in computed column

[ https://issues.apache.org/jira/browse/FLINK-20539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17774768#comment-17774768 ] xuyang commented on FLINK-20539: The cause is that in Flink, we always treat the ROW as a struct type

[jira] [Commented] (FLINK-32873) Add configuration to allow disabling SQL query hints

[ https://issues.apache.org/jira/browse/FLINK-32873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17754897#comment-17754897 ] xuyang commented on FLINK-32873: [~bvarghese] Although I think this option is necessary, what about

[jira] [Commented] (FLINK-27247) ScalarOperatorGens.numericCasting is not compatible with legacy behavior

[ https://issues.apache.org/jira/browse/FLINK-27247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17524689#comment-17524689 ] xuyang commented on FLINK-27247: +1 > ScalarOperatorGens.numericCasting is not compatible with legacy

[jira] [Commented] (FLINK-33489) LISTAGG with generating partial-final agg will case wrong result

[ https://issues.apache.org/jira/browse/FLINK-33489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17784273#comment-17784273 ] xuyang commented on FLINK-33489: For a quick fix, we can forbid generating final-partial agg with this

[jira] [Created] (FLINK-33489) LISTAGG with generating partial-final agg will case wrong result

xuyang created FLINK-33489: -- Summary: LISTAGG with generating partial-final agg will case wrong result Key: FLINK-33489 URL: https://issues.apache.org/jira/browse/FLINK-33489 Project: Flink Issue

[jira] [Updated] (FLINK-33489) LISTAGG with generating partial-final agg will cause wrong result

[ https://issues.apache.org/jira/browse/FLINK-33489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuyang updated FLINK-33489: --- Summary: LISTAGG with generating partial-final agg will cause wrong result (was: LISTAGG with generating

[jira] [Commented] (FLINK-32807) when i use emitUpdateWithRetract of udtagg,bug error

[ https://issues.apache.org/jira/browse/FLINK-32807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17784297#comment-17784297 ] xuyang commented on FLINK-32807: Hi, [~luca.yang] . I think this issue is duplicated with

[jira] [Created] (FLINK-27851) Join can't access the pk from source table

xuyang created FLINK-27851: -- Summary: Join can't access the pk from source table Key: FLINK-27851 URL: https://issues.apache.org/jira/browse/FLINK-27851 Project: Flink Issue Type: Bug

[jira] [Created] (FLINK-27853) FLIP-229: Introduces Join Hint for Flink SQL Batch Job

xuyang created FLINK-27853: -- Summary: FLIP-229: Introduces Join Hint for Flink SQL Batch Job Key: FLINK-27853 URL: https://issues.apache.org/jira/browse/FLINK-27853 Project: Flink Issue Type: New

[jira] [Created] (FLINK-27876) Error side is chosen in BatchPhysicalHashJoinRule when the join is Semi or Anti

xuyang created FLINK-27876: -- Summary: Error side is chosen in BatchPhysicalHashJoinRule when the join is Semi or Anti Key: FLINK-27876 URL: https://issues.apache.org/jira/browse/FLINK-27876 Project: Flink

[jira] [Commented] (FLINK-27867) SplitAggregateITCase fails on CI

[ https://issues.apache.org/jira/browse/FLINK-27867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17552622#comment-17552622 ] xuyang commented on FLINK-27867: Hi, is this duplicated with FLINK-27832? > SplitAggregateITCase fails

[jira] [Commented] (FLINK-27922) Flink SQL unique key lost when set table.exec.mini-batch.enabled=true

[ https://issues.apache.org/jira/browse/FLINK-27922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17552625#comment-17552625 ] xuyang commented on FLINK-27922: Hi, I think this is duplicated with FLINK-27851  . What do you think,

[jira] [Comment Edited] (FLINK-27953) using the original order to add the primary key in PushProjectIntoTableSourceScanRule

[ https://issues.apache.org/jira/browse/FLINK-27953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17556439#comment-17556439 ] xuyang edited comment on FLINK-27953 at 6/20/22 4:06 PM: - It seems it's a good

[jira] [Commented] (FLINK-27953) using the original order to add the primary key in PushProjectIntoTableSourceScanRule

[ https://issues.apache.org/jira/browse/FLINK-27953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17556439#comment-17556439 ] xuyang commented on FLINK-27953: It seems a good way to keep the origin order about projections to

[jira] [Updated] (FLINK-27952) Table UDF fails when using Double.POSITIVE_INFINITY as parameters

[ https://issues.apache.org/jira/browse/FLINK-27952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuyang updated FLINK-27952: --- Attachment: image-2022-06-21-00-19-12-151.png > Table UDF fails when using Double.POSITIVE_INFINITY as

[jira] [Created] (FLINK-28678) Support SQL hint for Filter, SetOp, Sort, Window, Values

xuyang created FLINK-28678: -- Summary: Support SQL hint for Filter, SetOp, Sort, Window, Values Key: FLINK-28678 URL: https://issues.apache.org/jira/browse/FLINK-28678 Project: Flink Issue Type: New

[jira] [Created] (FLINK-28682) support join hint in flink batch

xuyang created FLINK-28682: -- Summary: support join hint in flink batch Key: FLINK-28682 URL: https://issues.apache.org/jira/browse/FLINK-28682 Project: Flink Issue Type: Sub-task

[jira] [Updated] (FLINK-28678) Support SQL hint for Filter, SetOp, Sort, Window, Values

[ https://issues.apache.org/jira/browse/FLINK-28678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuyang updated FLINK-28678: --- Parent: FLINK-27853 Issue Type: Sub-task (was: New Feature) > Support SQL hint for Filter, SetOp,

[jira] [Updated] (FLINK-28678) Support SQL hint for Filter, SetOp, Sort, Window, Values

[ https://issues.apache.org/jira/browse/FLINK-28678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuyang updated FLINK-28678: --- Description: Ref CALCITE-5107 . Mainly cherry pick it. The following files should be removed from the

[jira] [Commented] (FLINK-28678) Support SQL hint for Filter, SetOp, Sort, Window, Values

[ https://issues.apache.org/jira/browse/FLINK-28678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17572267#comment-17572267 ] xuyang commented on FLINK-28678: Hi, thanks for your reminder, [~martijnvisser] . What about the new

[jira] [Commented] (FLINK-27239) rewrite PreValidateReWriter from scala to java

[ https://issues.apache.org/jira/browse/FLINK-27239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17522040#comment-17522040 ] xuyang commented on FLINK-27239: I'll try to fix it. > rewrite PreValidateReWriter from scala to java >

[jira] [Created] (FLINK-27239) rewrite PreValidateReWriter from scala to java

xuyang created FLINK-27239: -- Summary: rewrite PreValidateReWriter from scala to java Key: FLINK-27239 URL: https://issues.apache.org/jira/browse/FLINK-27239 Project: Flink Issue Type: Improvement

[jira] [Updated] (FLINK-29081) Join Hint cannot be identified by lowercase

[ https://issues.apache.org/jira/browse/FLINK-29081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuyang updated FLINK-29081: --- Fix Version/s: 1.16.0 Affects Version/s: 1.16.0 > Join Hint cannot be identified by lowercase >

[jira] [Commented] (FLINK-29087) Jdbc connector sql ITCase failed when run in idea

[ https://issues.apache.org/jira/browse/FLINK-29087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17583603#comment-17583603 ] xuyang commented on FLINK-29087: I'll try to fix it. > Jdbc connector sql ITCase failed when run in

[jira] [Created] (FLINK-29081) Join Hint cannot be identified by lowercase

xuyang created FLINK-29081: -- Summary: Join Hint cannot be identified by lowercase Key: FLINK-29081 URL: https://issues.apache.org/jira/browse/FLINK-29081 Project: Flink Issue Type: Bug

[jira] [Commented] (FLINK-28968) Release Testing: Verify FLIP-234 LOOKUP Hint

[ https://issues.apache.org/jira/browse/FLINK-28968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17583007#comment-17583007 ] xuyang commented on FLINK-28968: Hi, [~godfreyhe] , the testing is being carried out gradually and is

[jira] [Commented] (FLINK-28968) Release Testing: Verify FLIP-234 LOOKUP Hint

[ https://issues.apache.org/jira/browse/FLINK-28968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17599506#comment-17599506 ] xuyang commented on FLINK-28968: Hi, [~godfreyhe] . The test work is finished. > Release Testing:

[jira] [Created] (FLINK-29221) Adding join hint in sql may cause imcompatible state

xuyang created FLINK-29221: -- Summary: Adding join hint in sql may cause imcompatible state Key: FLINK-29221 URL: https://issues.apache.org/jira/browse/FLINK-29221 Project: Flink Issue Type:

[jira] [Created] (FLINK-29074) use 'add jar' in sql client throws "Could not find any jdbc dialect factories that implement"

xuyang created FLINK-29074: -- Summary: use 'add jar' in sql client throws "Could not find any jdbc dialect factories that implement" Key: FLINK-29074 URL: https://issues.apache.org/jira/browse/FLINK-29074

[jira] [Commented] (FLINK-28968) Release Testing: Verify FLIP-234 LOOKUP Hint

[ https://issues.apache.org/jira/browse/FLINK-28968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17585173#comment-17585173 ] xuyang commented on FLINK-28968: Hi,[~lincoln.86xy]. The testing work is finished, and it seems that

[jira] [Commented] (FLINK-28969) Release Testing: Verify FLIP-229 Join Hints for Flink SQL Batch

[ https://issues.apache.org/jira/browse/FLINK-28969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17596935#comment-17596935 ] xuyang commented on FLINK-28969: Thanks for your testing,[~lincoln.86xy] . I'll try to fix them. >

[jira] [Created] (FLINK-29280) Hint will not be propagated in subquery

xuyang created FLINK-29280: -- Summary: Hint will not be propagated in subquery Key: FLINK-29280 URL: https://issues.apache.org/jira/browse/FLINK-29280 Project: Flink Issue Type: Bug

[jira] [Updated] (FLINK-29280) Join hint are not propagated in subquery

[ https://issues.apache.org/jira/browse/FLINK-29280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuyang updated FLINK-29280: --- Summary: Join hint are not propagated in subquery (was: Join hint will not be propagated in subquery) >

[jira] [Updated] (FLINK-29280) Join hint will not be propagated in subquery

[ https://issues.apache.org/jira/browse/FLINK-29280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuyang updated FLINK-29280: --- Summary: Join hint will not be propagated in subquery (was: Hint will not be propagated in subquery) >

[jira] [Commented] (FLINK-29315) HDFSTest#testBlobServerRecovery fails on CI

[ https://issues.apache.org/jira/browse/FLINK-29315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17606387#comment-17606387 ] xuyang commented on FLINK-29315:

[jira] [Commented] (FLINK-26721) PulsarSourceITCase.testSavepoint failed on azure pipeline

[ https://issues.apache.org/jira/browse/FLINK-26721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17576479#comment-17576479 ] xuyang commented on FLINK-26721:

[jira] [Commented] (FLINK-28440) EventTimeWindowCheckpointingITCase.testSlidingTimeWindow failed with restore

[ https://issues.apache.org/jira/browse/FLINK-28440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17576483#comment-17576483 ] xuyang commented on FLINK-28440:

[jira] [Commented] (FLINK-28844) YARNHighAvailabilityITCase fails with NoSuchMethod of org.apache.curator

[ https://issues.apache.org/jira/browse/FLINK-28844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17576484#comment-17576484 ] xuyang commented on FLINK-28844:

[jira] [Created] (FLINK-28969) Release Testing: Verify FLIP-229 Join Hints for Flink SQL Batch

xuyang created FLINK-28969: -- Summary: Release Testing: Verify FLIP-229 Join Hints for Flink SQL Batch Key: FLINK-28969 URL: https://issues.apache.org/jira/browse/FLINK-28969 Project: Flink Issue

[jira] [Commented] (FLINK-28678) Support SQL hint for Filter, SetOp, Sort, Window, Values

[ https://issues.apache.org/jira/browse/FLINK-28678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17573515#comment-17573515 ] xuyang commented on FLINK-28678: [~martijnvisser] I copied these steps to FLINK-28744 > Support SQL

[jira] [Commented] (FLINK-28744) Upgrade Calcite version to 1.31

[ https://issues.apache.org/jira/browse/FLINK-28744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17573514#comment-17573514 ] xuyang commented on FLINK-28744: Just for reminding, the following files should be removed from the

[jira] [Updated] (FLINK-28678) Support SQL hint for Filter, SetOp, Sort, Window, Values

[ https://issues.apache.org/jira/browse/FLINK-28678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuyang updated FLINK-28678: --- Description: Ref CALCITE-5107 . Mainly cherry pick it. The following files should be removed from the

[jira] [Updated] (FLINK-34378) Minibatch join disrupted the original order of input records

[ https://issues.apache.org/jira/browse/FLINK-34378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuyang updated FLINK-34378: --- Description: I'm not sure if it's a bug. The following case can re-produce this situation. {code:java} //

[jira] [Commented] (FLINK-34378) Minibatch join disrupted the original order of input records

[ https://issues.apache.org/jira/browse/FLINK-34378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815054#comment-17815054 ] xuyang commented on FLINK-34378: [~lsy] The situation is that although I set the parallelism is "1", but

[jira] [Commented] (FLINK-34016) Janino compile failed when watermark with column by udf

[ https://issues.apache.org/jira/browse/FLINK-34016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815140#comment-17815140 ] xuyang commented on FLINK-34016: Hi, [~wczhu] I have found the root bug and will try to fix it. You can

[jira] [Commented] (FLINK-34376) FLINK SQL SUM() causes a precision error

[ https://issues.apache.org/jira/browse/FLINK-34376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815091#comment-17815091 ] xuyang commented on FLINK-34376: This bug is introduced by

[jira] [Commented] (FLINK-34211) Filtering on Column names with ?s fails for JDBC lookup join.

[ https://issues.apache.org/jira/browse/FLINK-34211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815118#comment-17815118 ] xuyang commented on FLINK-34211: Hi, [~davidradl] this Jira looks like an improvement, not a bug, right?

[jira] [Updated] (FLINK-34378) Minibatch join disrupted the original order of input records

[ https://issues.apache.org/jira/browse/FLINK-34378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuyang updated FLINK-34378: --- Description: I'm not sure if it's a bug. The following case can re-produce this situation. {code:java} //

[jira] [Commented] (FLINK-28693) Codegen failed if the watermark is defined on a columnByExpression

[ https://issues.apache.org/jira/browse/FLINK-28693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815141#comment-17815141 ] xuyang commented on FLINK-28693: This bug is caused by that the code generated by codegen references the

[jira] [Updated] (FLINK-34378) Minibatch join disrupted the original order of input records

[ https://issues.apache.org/jira/browse/FLINK-34378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuyang updated FLINK-34378: --- Description: I'm not sure if it's a bug. The following case can re-produce this situation. {code:java} //

[jira] [Commented] (FLINK-34381) `RelDataType#getFullTypeString` should be used to print in `RelTreeWriterImpl` if `withRowType` is true instead of `Object#toString`

[ https://issues.apache.org/jira/browse/FLINK-34381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17814700#comment-17814700 ] xuyang commented on FLINK-34381: I will try to fix it if this makes sense indeed. >

[jira] [Commented] (FLINK-34348) Release Testing: Verify FLINK-20281 Window aggregation supports changelog stream input

[ https://issues.apache.org/jira/browse/FLINK-34348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17815480#comment-17815480 ] xuyang commented on FLINK-34348: Hi, [~hackergin]. Thanks for your detailed testing. Overall, it seems

[jira] [Resolved] (FLINK-33489) LISTAGG with generating partial-final agg will cause wrong result

[ https://issues.apache.org/jira/browse/FLINK-33489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuyang resolved FLINK-33489. Resolution: Resolved > LISTAGG with generating partial-final agg will cause wrong result >

[jira] [Commented] (FLINK-33449) Support array_contains_seq function

[ https://issues.apache.org/jira/browse/FLINK-33449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17796532#comment-17796532 ] xuyang commented on FLINK-33449: Hi, [~leoyy] thanks for driving this. IMO, this type of function is

[jira] [Commented] (FLINK-33878) Many Keyed Operator extends `TableStreamOperator` which is marked without key.

[ https://issues.apache.org/jira/browse/FLINK-33878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17798405#comment-17798405 ] xuyang commented on FLINK-33878: cc [~qingyue]  > Many Keyed Operator extends `TableStreamOperator`

[jira] [Commented] (FLINK-33878) Many Keyed Operator extends `TableStreamOperator` which is marked without key.

[ https://issues.apache.org/jira/browse/FLINK-33878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17798406#comment-17798406 ] xuyang commented on FLINK-33878: Do you think we should fix it? If yes, I want to take this Jira and fix

[jira] [Updated] (FLINK-33878) Many Keyed Operators extends `TableStreamOperator` which is marked without key.

[ https://issues.apache.org/jira/browse/FLINK-33878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuyang updated FLINK-33878: --- Summary: Many Keyed Operators extends `TableStreamOperator` which is marked without key. (was: Many Keyed

[jira] [Created] (FLINK-33878) Many Keyed Operator extends `TableStreamOperator` which is marked without key.

xuyang created FLINK-33878: -- Summary: Many Keyed Operator extends `TableStreamOperator` which is marked without key. Key: FLINK-33878 URL: https://issues.apache.org/jira/browse/FLINK-33878 Project: Flink

[jira] [Commented] (FLINK-33449) Support array_contains_seq function

[ https://issues.apache.org/jira/browse/FLINK-33449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17796978#comment-17796978 ] xuyang commented on FLINK-33449: Hi, [~leoyy] , thanks for your explanation. After your description, I

[jira] [Commented] (FLINK-20281) Window aggregation supports changelog stream input

[ https://issues.apache.org/jira/browse/FLINK-20281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17800443#comment-17800443 ] xuyang commented on FLINK-20281: Can I take this Jira? > Window aggregation supports changelog stream

[jira] [Created] (FLINK-33941) Use field index instead of field name about window time column

xuyang created FLINK-33941: -- Summary: Use field index instead of field name about window time column Key: FLINK-33941 URL: https://issues.apache.org/jira/browse/FLINK-33941 Project: Flink Issue

[jira] [Commented] (FLINK-33490) Validate the name conflicts when creating view

[ https://issues.apache.org/jira/browse/FLINK-33490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799679#comment-17799679 ] xuyang commented on FLINK-33490: Hi, [~libenchao] .IIUC, do you mean we need to support the following

[jira] [Commented] (FLINK-33951) should use aggCallNeedRetractions instead of needRetraction to check retract method, orelse throw not implement retract method

[ https://issues.apache.org/jira/browse/FLINK-33951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17801631#comment-17801631 ] xuyang commented on FLINK-33951: I'm also a little curious about the background of this jira. BTW,

[jira] [Commented] (FLINK-33490) Validate the name conflicts when creating view

[ https://issues.apache.org/jira/browse/FLINK-33490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17801633#comment-17801633 ] xuyang commented on FLINK-33490: Hi, [~martijnvisser] . IIRC, the small Flip that we want to introduce

  1   2   3   >