chore: Reorganize feature logging in Go for better extensibility#2614
chore: Reorganize feature logging in Go for better extensibility#2614feast-ci-bot merged 2 commits intofeast-dev:masterfrom
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2614 +/- ##
==========================================
- Coverage 81.64% 81.60% -0.05%
==========================================
Files 161 161
Lines 13304 13307 +3
==========================================
- Hits 10862 10859 -3
- Misses 2442 2448 +6
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
go/cmd/server/server_test.go
Outdated
There was a problem hiding this comment.
Do we no longer need to clean up the generated log file?
There was a problem hiding this comment.
Yep, it's written to temp directory, which will be cleaned up by test framework
4ec8ccd to
f15b622
Compare
There was a problem hiding this comment.
I think this is a comment that is no longer needed as we have tests now.
There was a problem hiding this comment.
Are these not supported types?
There was a problem hiding this comment.
Yeah, there're Timestamp_ms and Date32 types that are not convertible to proto. We write Timestamp_s to parquet but somehow it's being read by Go parquet reader as Timestamp_ms. Reasons are unclear yet. Date32 is used system column log_date. We can skip it for now in tests.
go/internal/feast/logging/logger.go
Outdated
There was a problem hiding this comment.
I think this should also have error handling for writing batch.
There was a problem hiding this comment.
We cannot really handle this error. But added printing
go/internal/feast/logging/logger.go
Outdated
There was a problem hiding this comment.
Maybe add some comments here that specify that differentiates flushing from writing.
There was a problem hiding this comment.
Added comments to LogSink interface
go/internal/feast/logging/service.go
Outdated
There was a problem hiding this comment.
I think there should be comments explaining all of these fields
There was a problem hiding this comment.
Not used right now. Deleted
sdk/python/feast/feature_logging.py
Outdated
There was a problem hiding this comment.
Shouldn't the default sample rate be 0 for perf?
There was a problem hiding this comment.
The default behaviour is omission of LoggingConfig in feature service. In this case no logging happening. But if you added logging config then default sample_rate is 100%.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kevjumba, pyalex The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Signed-off-by: pyalex <[email protected]>
6f52c8f to
c7446f5
Compare
Signed-off-by: pyalex <[email protected]>
|
/lgtm |
Signed-off-by: pyalex [email protected]
What this PR does / why we need it:
This is mostly refactoring PR. This refactoring is needed before integrating Python API for feature logging in offline store.
Improvements:
Which issue(s) this PR fixes:
Fixes #