FW: RE: Flink JDBC connector release
Hi Sergey, It looks like the issue we saw was a caused by a mismatch in our build levels, so was a false negative; and is not an issue. We are testing with the latest level of the branch now (the one compiled against 1.16). Kind regards, David. From: David Radley Date: Sunday, 4 February 2024 at 22:50 To: dev@flink.apache.org Subject: FW: [EXTERNAL] RE: Flink JDBC connector release Hi Sergey, Sorry for the typos. I meant: Yes that is right, I am talking about the jdbc connector rc3 and Flink 1.18. I am looking into finding a simple way to reproduce the issue, and will raise a Jira if I can, Kind regards, David. From: Sergey Nuyanzin Date: Friday, 2 February 2024 at 19:46 To: dev@flink.apache.org Subject: [EXTERNAL] Re: Flink JDBC connector release Hi David thanks for testing I assume you are talking about jdbc connector rc3 and Flink 1.18. In case you think there is a bug it would make sense to raise a jira issue and provide steps to reproduce it On Fri, Feb 2, 2024 at 5:42 PM David Radley wrote: > Hi, > > We have been doing some testing on flink jdbc connector rc2. We are > testing with Flink 1.1.8 jars and are using the TableEnvironment > TableResult< > https://nightlies.apache.org/flink/flink-docs-master/api/java/org/apache/flink/table/api/TableResult.html > > > executeSql(String< > http://docs.oracle.com/javase/7/docs/api/java/lang/String.html?is-external=true > > > statement). We hit some strange behaviour testing the lookup join, we got a > null pointer Exception on > https://github.com/apache/flink-connector-jdbc/blob/390d7bc9139204fbfc48fe275a69eb60c4807fb5/flink-connector-jdbc/src/main/java/org/apache/flink/connector/jdbc/table/JdbcRowDataLookupFunction.java#L192 > > and that the constructor did not seem to be driven. We changed the > release that the pom file was building against to 1.18 and it works; so our > issue appeared to be mismatching jar levels. This issue did not appear > running the SQL client against rc2. > > > > I am attempting to put a simple java test together to show this issue. > > > > WDYT? > > Kind regards. > > > > > > > > Unless otherwise stated above: > > IBM United Kingdom Limited > Registered in England and Wales with number 741598 > Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU > -- Best regards, Sergey Unless otherwise stated above: IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU Unless otherwise stated above: IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU
FW: RE: Flink JDBC connector release
Hi Sergey, Sorry for the typos. I meant: Yes that is right, I am talking about the jdbc connector rc3 and Flink 1.18. I am looking into finding a simple way to reproduce the issue, and will raise a Jira if I can, Kind regards, David. From: Sergey Nuyanzin Date: Friday, 2 February 2024 at 19:46 To: dev@flink.apache.org Subject: [EXTERNAL] Re: Flink JDBC connector release Hi David thanks for testing I assume you are talking about jdbc connector rc3 and Flink 1.18. In case you think there is a bug it would make sense to raise a jira issue and provide steps to reproduce it On Fri, Feb 2, 2024 at 5:42 PM David Radley wrote: > Hi, > > We have been doing some testing on flink jdbc connector rc2. We are > testing with Flink 1.1.8 jars and are using the TableEnvironment > TableResult< > https://nightlies.apache.org/flink/flink-docs-master/api/java/org/apache/flink/table/api/TableResult.html > > > executeSql(String< > http://docs.oracle.com/javase/7/docs/api/java/lang/String.html?is-external=true > > > statement). We hit some strange behaviour testing the lookup join, we got a > null pointer Exception on > https://github.com/apache/flink-connector-jdbc/blob/390d7bc9139204fbfc48fe275a69eb60c4807fb5/flink-connector-jdbc/src/main/java/org/apache/flink/connector/jdbc/table/JdbcRowDataLookupFunction.java#L192 > > and that the constructor did not seem to be driven. We changed the > release that the pom file was building against to 1.18 and it works; so our > issue appeared to be mismatching jar levels. This issue did not appear > running the SQL client against rc2. > > > > I am attempting to put a simple java test together to show this issue. > > > > WDYT? > > Kind regards. > > > > > > > > Unless otherwise stated above: > > IBM United Kingdom Limited > Registered in England and Wales with number 741598 > Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU > -- Best regards, Sergey Unless otherwise stated above: IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU Unless otherwise stated above: IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU
RE: Flink JDBC connector release
Hi Sergey, Yes that is right I am talking about are talking about jdbc connector rc3 and Flink 1.18. I am looking into finding a simple way to reproduce it, and will raise a Jira if I can, Kind regards, David. From: Sergey Nuyanzin Date: Friday, 2 February 2024 at 19:46 To: dev@flink.apache.org Subject: [EXTERNAL] Re: Flink JDBC connector release Hi David thanks for testing I assume you are talking about jdbc connector rc3 and Flink 1.18. In case you think there is a bug it would make sense to raise a jira issue and provide steps to reproduce it On Fri, Feb 2, 2024 at 5:42 PM David Radley wrote: > Hi, > > We have been doing some testing on flink jdbc connector rc2. We are > testing with Flink 1.1.8 jars and are using the TableEnvironment > TableResult< > https://nightlies.apache.org/flink/flink-docs-master/api/java/org/apache/flink/table/api/TableResult.html > > > executeSql(String< > http://docs.oracle.com/javase/7/docs/api/java/lang/String.html?is-external=true > > > statement). We hit some strange behaviour testing the lookup join, we got a > null pointer Exception on > https://github.com/apache/flink-connector-jdbc/blob/390d7bc9139204fbfc48fe275a69eb60c4807fb5/flink-connector-jdbc/src/main/java/org/apache/flink/connector/jdbc/table/JdbcRowDataLookupFunction.java#L192 > > and that the constructor did not seem to be driven. We changed the > release that the pom file was building against to 1.18 and it works; so our > issue appeared to be mismatching jar levels. This issue did not appear > running the SQL client against rc2. > > > > I am attempting to put a simple java test together to show this issue. > > > > WDYT? > > Kind regards. > > > > > > > > Unless otherwise stated above: > > IBM United Kingdom Limited > Registered in England and Wales with number 741598 > Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU > -- Best regards, Sergey Unless otherwise stated above: IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU
Re: Flink JDBC connector release
Hi David thanks for testing I assume you are talking about jdbc connector rc3 and Flink 1.18. In case you think there is a bug it would make sense to raise a jira issue and provide steps to reproduce it On Fri, Feb 2, 2024 at 5:42 PM David Radley wrote: > Hi, > > We have been doing some testing on flink jdbc connector rc2. We are > testing with Flink 1.1.8 jars and are using the TableEnvironment > TableResult< > https://nightlies.apache.org/flink/flink-docs-master/api/java/org/apache/flink/table/api/TableResult.html> > executeSql(String< > http://docs.oracle.com/javase/7/docs/api/java/lang/String.html?is-external=true> > statement). We hit some strange behaviour testing the lookup join, we got a > null pointer Exception on > https://github.com/apache/flink-connector-jdbc/blob/390d7bc9139204fbfc48fe275a69eb60c4807fb5/flink-connector-jdbc/src/main/java/org/apache/flink/connector/jdbc/table/JdbcRowDataLookupFunction.java#L192 > > and that the constructor did not seem to be driven. We changed the > release that the pom file was building against to 1.18 and it works; so our > issue appeared to be mismatching jar levels. This issue did not appear > running the SQL client against rc2. > > > > I am attempting to put a simple java test together to show this issue. > > > > WDYT? > > Kind regards. > > > > > > > > Unless otherwise stated above: > > IBM United Kingdom Limited > Registered in England and Wales with number 741598 > Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU > -- Best regards, Sergey
