Skip to content
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

When importing data through insert, the data is filtered out #45470

Open
LJ1An opened this issue May 11, 2024 · 0 comments
Open

When importing data through insert, the data is filtered out #45470

LJ1An opened this issue May 11, 2024 · 0 comments
Labels
type/bug Something isn't working

Comments

@LJ1An
Copy link

LJ1An commented May 11, 2024

Steps to reproduce the behavior (Required)

INSERT OVERWRITE 【db_name.table_name】 WITH LABEL insert_load_table_name SELECT column1,column2,...... FROM 【mysql_catalog.db_name.table_name】

Expected behavior (Required)

The number of rows for 【db_name.table_name】 and 【mysql_catalog.db_name.table_name】 is the same

Real behavior (Required)

 【db_name.table_name】 has less data than 【mysql_catalog.db_name.table_name】. Some data has been filtered, and by checking the value of field trackingSQL in command 【show load from db_name where label like 'insert_load_table_name'】, it was found that it was due to some column length values in table【mysql_catalog.db_name.table_name】 exceeding the maximum value of varchar.
 I would like to add an optional configuration where when the length value of a field exceeds the maximum value of varchar, the field value is set to null instead of filtering out the entire row.

StarRocks version (Required)

3.1.5-5d8438a

@LJ1An LJ1An added the type/bug Something isn't working label May 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant