Skip to content

Conversation

@ilangofman
Copy link
Owner

@ilangofman ilangofman commented Jul 29, 2021

Signed-off-by: ilangofman igofman99@gmail.com

What this PR does:

As part of the series deletion API proposal using block storage, this PR is responsible for implementing the query time filtering.

From the compactor, it writes to the bucket index the tombstones that are required for filtering. Afterwards, the queriers load the tombstones and apply the filtering using them.

Note: this is only implemented using the bucket index. If it is not enabled, then the query time filtering will not work (as per the proposal).

Which issue(s) this PR fixes:
Fixes #

Checklist

  • Tests updated
  • Documentation added
  • CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX]

ilangofman and others added 6 commits July 29, 2021 13:15
Signed-off-by: ilangofman <igofman99@gmail.com>
Signed-off-by: ilangofman <igofman99@gmail.com>
Signed-off-by: ilangofman <igofman99@gmail.com>
Signed-off-by: ilangofman <igofman99@gmail.com>
return t, nil
}

func (w *Updater) isTombstoneForFiltering(t *cortex_tsdb.Tombstone) bool {
Copy link

@harry671003 harry671003 Aug 9, 2021

Choose a reason for hiding this comment

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

Shouldn't this be in tombstones.go?

bkt: bucket.NewUserBucketClient(userID, bkt, cfgProvider),
logger: util_log.WithUserID(userID, logger),
bkt: bucket.NewUserBucketClient(userID, bkt, cfgProvider),
blocksDeletionDelay: deletionDelay,

Choose a reason for hiding this comment

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

Are these only used in isTombstoneForFiltering(). I don't think that method should belong in this class.

Signed-off-by: ilangofman <igofman99@gmail.com>
Signed-off-by: ilangofman <igofman99@gmail.com>
Signed-off-by: ilangofman <igofman99@gmail.com>
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.

3 participants