-
-
Notifications
You must be signed in to change notification settings - Fork 39
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
BCP import and column name starting with number fails #511
Comments
Hey @isaacrlee , I think it's something else. Below worked fine for me: source: postgres
target: mssql
streams:
test1k_mysql_pg:
sql: select id as "1col", id as "_1col" from public.test1k_mysql_pg
object: dbo.test1k_mysql_pg
mode: full-refresh
|
I see you're using v15. can you try with bcp version 17? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue Description
Description of the issue: When trying to import data from a table (Snowflake in my case) with a column that has a name starting with a number (e.g. "123col") to SQL Server, the replication fails if
use_bulk
is set totrue
. Whenuse_bulk
is set tofalse
, the replication succeeds. In the logs, I see there is some logic to handle columns that are named like that as I'm seeing both the column name with a_
prefix and without in the created temp tablee.g. create table "test"."test_int_col_sling_tmp" ("_123col" bigint, "123col" bigint)
. It feels like this has unhandled consequences for the BCP flow. If there's anything I can do to help with investigation for this admittedly very specific edge case, please let me know.Sling version (
sling --version
): 1.4.3Operating System (
linux
,mac
,windows
): WindowsReplication Configuration:
-d
):The text was updated successfully, but these errors were encountered: