-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Support delete with predicate functionality via /api/v2/delete #19635
Comments
Update: I'm in the thick of it and there's more code to move over from |
Per discussions with the 2.0 GA team this is being de-prioritised in favour of backup and restore: |
The tests are currently failing due to the removal of the delete-with-predictate API. It was removed in influxdata/influxdb#19580 and there is an open issue for restoring it in influxdata/influxdb#19635.
The tests are currently failing due to the removal of the delete-with-predictate API. It was removed in influxdata/influxdb#19580 and there is an open issue for restoring it in influxdata/influxdb#19635.
I'm sorry to ask a seemingly stupid question, but im trying to delete data using CLI for nearly an hour now (and also tried the curl method). My last tries where looking like that: |
@cgfoed For OSS, this issue states that it isn't possible to selective delete data. You have to drop the entire bucket until this issue is resolved. |
When is this issue expected to be resolved? Not managing to delete data is a big issue. |
I'm not even able to delete without predicate, and backup/restore is not really an alternative IMHO. I understand that OSS is probably lower priority because we aren't paying, but please consider fixing this quickly. |
While waiting, what we do is delete buckets :/
…On Wed, Dec 2, 2020 at 4:23 AM Mihir Patil ***@***.***> wrote:
I'm not even able to delete without predicate, and backup/restore is not
really an alternative IMHO.
I understand that OSS is probably lower priority because we aren't paying,
but please consider fixing this quickly.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#19635 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABQVJDU4RG75WXVULR475R3SSWXL7ANCNFSM4RYSBZFA>
.
|
Pending PR for the fix: #20236 |
Thanks! |
plan is to drop this into 2.0.3 early next week. |
Thanks for fixing this. However, I must say that this is not the first "surprise" while using what is supposed to be "GA version". Seems like your marketing department runs far ahead of development. As a result: trying to migrate my project to Influx 2x looked like a premature decision in hindsight and I ended up wasting quite some time. |
What
To ensure feature parity with Cloud 2.0, InfluxDB OSS 2.0 requires an implementation of the delete with predicate API via
/api/v2/delete
. This will require enhancements to thetsdb
package and storage engine.Background
The API was disabled per #19580 and returns
501 Not Implemented
as there was no equivalent 1.x tsdb storage API to support this feature. The followingDeleteSeries
API was evaluatedinfluxdb/tsdb/store.go
Line 1266 in b917d8d
however, due to differences between series keys in TSM 2.0 vs 1.x, it is unable to support fine-grained delete functionality for a predicate that targets a specific field:
The text was updated successfully, but these errors were encountered: