-
Notifications
You must be signed in to change notification settings - Fork 817
Implementing Parquet Converter #6716
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
base: master
Are you sure you want to change the base?
Conversation
b0c7c06
to
2eec8b9
Compare
Signed-off-by: alanprot <[email protected]>
57efb1c
to
5e75bc8
Compare
Signed-off-by: alanprot <[email protected]>
5e75bc8
to
d820fd5
Compare
) | ||
|
||
type CompactionMark struct { | ||
Version int `json:"version"` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we can add a comment about what this version actually means. It is the same as the version of the parquet file schema and updating version will trigger a rewrite of the parquet file?
Signed-off-by: alanprot <[email protected]>
Signed-off-by: alanprot <[email protected]>
Signed-off-by: alanprot <[email protected]>
Signed-off-by: alanprot <[email protected]>
01a64a4
to
2497df1
Compare
Signed-off-by: alanprot <[email protected]>
2497df1
to
46e3114
Compare
3d72c44
to
cc6d121
Compare
Signed-off-by: alanprot <[email protected]>
cc6d121
to
4fa4df6
Compare
Signed-off-by: alanprot <[email protected]>
fa8300a
to
1c8eda0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's add a changelog for this feature? Even though it is a hidden feature now still worth a changelog
@@ -113,6 +114,7 @@ type Config struct { | |||
QueryRange queryrange.Config `yaml:"query_range"` | |||
BlocksStorage tsdb.BlocksStorageConfig `yaml:"blocks_storage"` | |||
Compactor compactor.Config `yaml:"compactor"` | |||
ParquetConverter parquetconverter.Config `yaml:"parquet_converter" doc:"hidden"` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we usually mark a new component config as hidden?
Should we still add parquet storage feature as experimental in v1 guarantee?
|
||
const ( | ||
ConverterMarkerFileName = "parquet-converter-mark.json" | ||
CurrentVersion = 1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How do we plan to use CurrentVersion
?
It is a version that bumps when we changes format of the ConverterMark
file or parquet file
@@ -40,6 +42,10 @@ func NoCompactMarkFilenameMarkFilepath(blockID ulid.ULID) string { | |||
return fmt.Sprintf("%s/%s-%s", MarkersPathname, blockID.String(), metadata.NoCompactMarkFilename) | |||
} | |||
|
|||
func ConverterMarkFilePath(blockID ulid.ULID) string { | |||
return fmt.Sprintf("%s/%s-%s", MarkersPathname, blockID.String(), parquet.ConverterMarkerFileName) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we use a different marker path for parquet converter marker? Like parquet-markers/<blockID>-<marker-name>
.
To avoid too many files inside the existing markers folder. It is also ok to use current path
if err != nil { | ||
if userBkt.IsObjNotFoundErr(err) { | ||
return &ConverterMark{}, nil | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to handle IsAccessDeniedErr
?
What this PR does:
Implementing parquet converter:
The documentation of this component is hidden for now as the feature is not code complete (We need to create the parquet queriable).
Which issue(s) this PR fixes:
Partially Fixes #6712
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]