New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

addBatch INSERT not using the column order if specified in the INSERT statement #124

Open
dwayneberry opened this Issue Oct 26, 2017 · 1 comment

Comments

Projects
None yet
2 participants
@dwayneberry
Copy link
Collaborator

dwayneberry commented Oct 26, 2017

see

https://community.mapd.com/t/mapd-java-jdbc-preparedstatement-bug/693/2

When we fix this we should also convert the api call over to use load_table_binary_columnar

@randyzwitch

This comment has been minimized.

Copy link
Collaborator

randyzwitch commented Oct 29, 2018

@niviksha It would be great if we could prioritize a fix for this, as it has downstream impacts with other data ingestion tools (Streamsets specifically in my case). When loading data in batch, JDBC doesn't respect the column order, instead alphabetizing the columns. This is a pretty odd limitation, and one that's hard to understand from an end user's perspective.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment