-
Notifications
You must be signed in to change notification settings - Fork 11
Timestamp Configs for FlatPostgresCollection #274
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
Open
suddendust
wants to merge
10
commits into
hypertrace:main
Choose a base branch
from
suddendust:pg_writes_timestampConfig
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+458
−3
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #274 +/- ##
============================================
+ Coverage 80.65% 80.71% +0.05%
- Complexity 1396 1403 +7
============================================
Files 240 241 +1
Lines 6871 6926 +55
Branches 638 646 +8
============================================
+ Hits 5542 5590 +48
- Misses 914 916 +2
- Partials 415 420 +5
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
…pg_writes_timestampConfig
This reverts commit e86721a.
|
This will be doable at what level? Per table ? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Config-Driven Timestamp Fields for Flat Collections
Summary
Adds auto-managed
createdTimeandlastUpdateTimefields for flat PostgreSQL collections, configurable viaPostgresClientcustom parameters.Changes
BIGINT→ epoch millis,TIMESTAMPTZ→java.sql.Timestamp, etc.)createdTimepreserved on updates,lastUpdateTimealways updatedNULLTesting
testTimestampsOnCreate- Validates both fields populated on createtestTimestampsOnUpsert- ValidatescreatedTimepreserved,lastUpdateTimeupdatedtestNoExceptionWhenTimestampConfigMissing- Validates graceful handling when config absent