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

fix: respect nullable settings in arrow schema #264

Merged
merged 1 commit into from
Oct 15, 2024

Conversation

v0y4g3r
Copy link
Contributor

@v0y4g3r v0y4g3r commented Oct 11, 2024

Update the nullable settings of fields that are actually nullable in arrow schema.

 Reorganize imports and update nullable fields in Arrow schemas

 - Reorder imports in components.go for clarity
 - Make HistogramSum, HistogramMin, and HistogramMax fields nullable in Arrow schemas for ehistogram_dp.go, histogram_dp.go, and number_data_point.go
 - Remove empty connector factory map initialization in components.go
 - Swap import order in main_windows.go for consistency
Copy link
Contributor

@jmacd jmacd left a comment

Choose a reason for hiding this comment

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

Looks good to me. @lquerel PTAL.
Histogram sums are optional according to the data model specification; Prometheus doesn't want them if they're not monotonic and the data model and protocol support histograms with negative values.

@lquerel
Copy link
Contributor

lquerel commented Oct 15, 2024

LGTM. Thanks for this fix.

@lquerel lquerel merged commit 971440e into open-telemetry:main Oct 15, 2024
2 checks passed
Copy link
Contributor

@lquerel lquerel left a comment

Choose a reason for hiding this comment

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

LGTM

@jmacd jmacd mentioned this pull request Oct 17, 2024
jmacd added a commit that referenced this pull request Oct 17, 2024
- Fix nullable setting in Arrow schema.
[#264](#264)
- Fix bucket count used in test histogram data.
[#265](#265)
- Update to v0.111.0 collector dependencies; concurrent batch processor
component name fix.
[#266](#266)
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.

Incorrect nullable setting in Arrow schema
3 participants