Repository navigation
Use automatic schema for session parquet files - #324
byKryptogram wants to merge 1 commit into
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
| Layer / File(s) | Summary |
|---|---|
sessionData types and inferred schema pkg/runner/session.go |
sessionData uses uint fields and byte slices. newSession stores values directly and clones message bytes. sessionDataSchema is removed. writeSessionParquet uses the inferred schema. |
Test fixtures for new field types pkg/runner/session_test.go, pkg/runner/data_collector_test.go, pkg/runner/manual_parquet_rotation_test.go, pkg/runner/parquet_files_test.go |
Tests set ServerID as []byte. Session tests use unsigned pointers and create the writer without an explicit schema. Assertions compare ServerID as bytes. |
Priority:
Estimated code review effort: 2 (Simple) | ~15 minutes
Change: Refactor
Suggested reviewers: linkdata
Merge Risk: 
Minimal · previous review ed436
-
The identified identity and schema concerns do not block merging; normal checks remain appropriate.
🚥 Pre-merge checks | ✅ 4 | ❌ 1
-
❌ Failed checks (1 warning)
Check name Status Explanation Resolution Docstring Coverage ⚠️ WarningDocstring coverage is 11.11% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 9 functions across 5 files. Write docstrings for the functions missing them to satisfy the coverage threshold. ✅ Passed checks (4 passed)
-
Check name Status Explanation Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request. Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request. Title check ✅ Passed The title clearly and concisely describes the main change: using the automatic schema for session Parquet files. Description check ✅ Passed The description explains that the change uses shorter integer support from parquet-go to remove the manual schema and its sorting drawback.
-
✨ Finishing Touches: 💡 1
-
📝 Generate docstrings: 💡
-
- Commit to this branch
- Create a new PR
🧪 Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
Comment @coderabbitai help to get the list of available commands.
ed43677 to
3e924b0
Compare
|
ping @morkrost |
8d809d3 to
5586a37
Compare
|
Fix: ServerID []byte `parquet:"server_id,optional"`
QueryMessage []byte `parquet:"query_message,optional"`
ResponseMessage []byte `parquet:"response_message,optional"`A round-trip test that writes a query-only session and checks that |
Our dependency github.com/parquet-go/parquet-go has now implemented support for shorter integers, use them to avoid having to define a manual schema and avoid the sorting drawback.
5586a37 to
b326e1f
Compare
@linkdata: During my testing the struct fields could already result in a |
Our dependency
github.com/parquet-go/parquet-gohas now implemented support for shorter integers, use them to avoid having to define a manual schema and avoid the sorting drawback.