Skip to content

Do not persist inf/nan floating point stats in metastore#2471

Merged
findepi merged 1 commit intotrinodb:masterfrom
findepi:doublestats
Jan 13, 2020
Merged

Do not persist inf/nan floating point stats in metastore#2471
findepi merged 1 commit intotrinodb:masterfrom
findepi:doublestats

Conversation

@findepi
Copy link
Member

@findepi findepi commented Jan 10, 2020

Hive metastore does not accept infinity or NaN values.

@cla-bot cla-bot bot added the cla-signed label Jan 10, 2020
@findepi findepi requested a review from kokosing January 11, 2020 15:49
Copy link
Member

@kokosing kokosing left a comment

Choose a reason for hiding this comment

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

Is this something that could be supported in certain version of HMS? Maybe GLUE supports that?
Personally, I don't see a reason why inf values are bad. Other than that it is hard to calculate anything with this.

@findepi
Copy link
Member Author

findepi commented Jan 11, 2020

@kokosing there is no advantage from storing max=inf. The only information it carries is that data didn't contain NaN.
But we can't really make use of this information, so 🤷‍♂.

Hive metastore does not accept infinity or NaN values.
@findepi
Copy link
Member Author

findepi commented Jan 11, 2020

CI failed -- #2467

@findepi findepi merged commit 37918db into trinodb:master Jan 13, 2020
@findepi findepi deleted the doublestats branch January 13, 2020 08:20
@findepi findepi added this to the 329 milestone Jan 13, 2020
@findepi findepi mentioned this pull request Jan 13, 2020
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

2 participants