Passing datetime2/date via ISQLServerBulkRecord is throwing exception

[SubashRoul]

Driver version or jar name

mssql-jdbc-6.2.1.jre8.jar

Java/JVM version

java version "1.8.0_152"
Java(TM) SE Runtime Environment (build 1.8.0_152-b16)

Problem description

For Azure SQL Data Warehouse, passing datetime2 via ISQLServerBulkRecord throws Received an invalid column length from the bcp client for colid modify_time. Same error for date type columns.

I have tried the example codes given in issue #161 with datetime2 and date columns.

For datetime2, I am passing the following parameters.
columnType : java.sql.Types.TIMESTAMP
precision : 0
scale : 0

For date,
columnType : java.sql.Types.DATE
precision : 0
scale : 0

[peterbae]

Hi @SubashRoul, to implement a solution for this issue, I need to implement #161 as well, and it seems like it's going to take more time than i originally thought. I've left a comment in my PR (closed now) regarding my progress, and I will return to this issue at a later time.

[abhijeethp]

Hello @peterbae @cheenamalhotra ,
is this still a work in progress?
cc @saksham1711 @tgorthi

[peterbae]

It's in our backlog for now, but we don't have a timeline for this issue yet.

[FelipeBR2]

Hi, as #161 is now closed, do you have a timeline for this topic?

[Jeffery-Wasty]

While this has been in the backlog for a while, there is no current timeline. We'll take a look at it during out next planning and provide updates as necessary.

[FelipeBR2]

Hello @Jeffery-Wasty , could you please prioritize this issue as it has a very high business impact for the Robert Bosch GmbH? We use the azure data warehouse as part of an analytical procedure to optimize our blocked inventory on a global level at Bosch. We require this bulk upload because thousands of records needs to be update simultaneously which also includes the Datetime data type which is currently not working with the JDBC driver.

If you have further questions, please contact me at [email protected]

[Jeffery-Wasty]

Hi @FelipeBR2,

Thank you for your patience, we have a team member looking into the issue at the moment.

[lilgreenbird]

hi @FelipeBR2

Could you please try this again using the latest 12.1.0 release? 6.2.1 is quite old we've had some fixes in this area and I rem specifically there was a fix for an issue which resulted in this error message. If you still see this issue in the latest release please provide a standalone java app and schema that reproduces the issue.

Thanks.

[FelipeBR2]

Hi @lilgreenbird. Thanks for the quick response.

As I`m currently out of office for today, tomorrow I will try to get the latest version and see if the issue has been fixed.

[FelipeBR2]

Hi, sorry for the delayed response, got quite some work regarding end of the year. I was able to test the new version 12.1.0, but unfortunally, I still got the error

[lilgreenbird]

Could please provide a standalone java app and schema that reproduces the issue? Thanks.

[FelipeBR2]

I'm utilizing KNIME in this specific case. I have been talking to their team as well regarding this issue.
I only have the workflow, but as it contains sensitive information I cannot send it

[tkyc]

Just to clarify, this issue is still backlogged and isn't implemented at the moment as the initial implementation #568 did not fully solve the problem. #161 was not a PR but a tangent issue.

We'll revisit this during triage for the new semester.