Skip to content
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

ingest: Default index pipeline not being applied to docs during bulk indexing #36144

Closed
rfraposa opened this issue Dec 2, 2018 · 8 comments
Closed
Labels
:Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP

Comments

@rfraposa
Copy link

rfraposa commented Dec 2, 2018

Elasticsearch version (bin/elasticsearch --version): 6.5.1

Description of the problem including expected versus actual behavior: I am indexing a Google spreadsheet (using the add-on: https://github.com/elastic/google-sheets-add-on) into a 6.5.1 cluster. The index has a default pipeline defined, which works as expected if I use _bulk from within Console. But the pipeline is not being applied to docs indexed using a _bulk insert from the JavaScript code.

@jakelandis jakelandis added the :Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP label Dec 2, 2018
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-features

@jakelandis
Copy link
Contributor

@rfraposa - could this be a due to #35817 ? (Console doesn't do anything special with the request)

If so, can we close as a duplicate ?

@rfraposa
Copy link
Author

rfraposa commented Dec 2, 2018

I don't know if it is the same issue, but it might be. The JavaScript code is not using any aliases - the _bulk command uses the actual index name.

@jakelandis
Copy link
Contributor

Is it possible to grab the http requests that are being sent from JavaScript ?

Or can you provide a reproduction scenario ?

@rfraposa
Copy link
Author

rfraposa commented Dec 3, 2018

I don't seem to be able to see the requests - not sure why. I'll PM you a link to a google doc with everyone configured and ready for testing.

@rfraposa
Copy link
Author

rfraposa commented Dec 3, 2018

Sorry @jakelandis - I don't know how the Add-On works, but it appears to use a callback mechanism. The data is not posted from my browser, so I can't see the _bulk command.

At any rate, my guess is that this is a duplicate of #35817 - it's the only thing that makes sense.

@jakelandis
Copy link
Contributor

closing and will take a closer look outside of this issue.

@jakelandis
Copy link
Contributor

I believe the root cause of this issue is #36219 (which was uncovered by investigating this issue) thanks for report @rfraposa !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP
Projects
None yet
Development

No branches or pull requests

3 participants