-
Notifications
You must be signed in to change notification settings - Fork 22
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
Unauthorized esdedupe #11
Comments
Try using the latest version:
if you're using SSL, please use the
|
@deric it's the same issue..
so its giving below error and my given key name is correct
|
That looks like different error than
|
Yes it's possible it's not in all all documents.
.
…On Fri, Oct 1, 2021, 7:11 PM Tomas Barton ***@***.***> wrote:
That looks like different error than Unauthorized to me.
source_ip field is probably not included in all documents. Try running
the command with higher verbosity:
docker run -it --rm deric/es-dedupe:latest esdedupe -H ***@***.*** -P 9200 -i "myindex" -f source_ip,feed_provider --level DEBUG --es-level DEBUG
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#11 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB6CDOJ7NNWGTGQDLP7X46LUEW275ANCNFSM5E7A4BHA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Then you can't use it as part of an unique key. I'll try to throw a better error message. |
Ok... So is there any other way to delete ?
Because I needed this things .
…On Fri, Oct 1, 2021, 7:32 PM Tomas Barton ***@***.***> wrote:
Then you can't use it as part of an unique key. I'll try to throw a better
error message.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#11 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB6CDOMU4VBE4MLBWHXLIBTUEW5QFANCNFSM5E7A4BHA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
@deric if the key field does not exist that I have fixed using the below method.
|
@dipenpatel235 That's not really a fix, rather a dirty-bomb which might lead to deleting all data from an index, if incorrect field name is used. |
Yes right...
But something you can put restrictions on that if we can find better way..
But as of now I have did that for my custom solution.
…On Mon, Oct 4, 2021, 6:03 PM Tomas Barton ***@***.***> wrote:
@dipenpatel235 <https://github.com/dipenpatel235> That's not really a
fix, rather a dirty-bomb which might lead to deleting all data from an
index, if incorrect field name is used.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#11 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB6CDOLWDWAWEL2PJ7BNRX3UFGNLDANCNFSM5E7A4BHA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
I had the same issue when passing |
i try below command and get error unauthorized.
The text was updated successfully, but these errors were encountered: