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

Feature/decimal support using float #1589

Merged

Conversation

gcca
Copy link
Contributor

@gcca gcca commented Aug 4, 2021

Fixes #1588

@gcca gcca requested a review from wmalpica August 4, 2021 15:59
@gcca gcca self-assigned this Aug 4, 2021
@GPUtester
Copy link
Collaborator

Please update the changelog in order to start CI tests.

View the gpuCI docs here.

@gcca gcca requested a review from felipeblazing August 4, 2021 16:46
for(size_t column_i = 0; column_i < column_indices.size(); column_i++) {
col_names[column_i] = schema.get_name(column_indices[column_i]);
cudf::type_id type_id = schema.get_dtype(column_indices[column_i]);

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How is this checking for decimals here its checking for float64. What if the file had contained a float64 and not a decimal?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I ask because you do decimal_cols.emplace_back below

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I had the same question and verified the it works just fine if there are floats and decimals or just one or just the other.

@wmalpica wmalpica merged commit 9826a15 into BlazingDB:branch-21.08 Aug 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[BUG] Add temporary DECIMAL support by using float64 instead
4 participants