-
Notifications
You must be signed in to change notification settings - Fork 24.4k
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
Remove support for Visio and potm files #23214
Remove support for Visio and potm files #23214
Conversation
as #22963 has been merged, I pushed new changes which makes more obvious that we are removing support for @jasontedor It's ready for review. @clintongormley I'd like to push it as well in 5.3 and 5.2 branches as it's a bug fix. Do you agree? |
Can you please rebase this as currently there are conflicts with the target branch? I'm fine with thing going into 5.3, I'm not fine with this going into 5.2. |
Can you refresh your browser? I don't see the conflict on my side. |
It's not a browser refresh issue.
|
Hmmm. Why do you rebase instead of merging? I understand why rebase is failing on the second commit but it should not be an issue because of the next commits. |
Because that's what you're going to go when you merge the commit it, and that's why GitHub is already showing you the conflict. |
Also, that's not how rebasing works. Rebasing replays every commit and halts on conflict. |
Note that I merged 5.x in my branch with the 3rd commit. |
I understand why you see this conflict and I don't. You defined rebase and merge as the default way to merge. I didn't. So if you don't rebase there is no conflict. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Please squash when merging.
* Send a non supported document to an ingest pipeline using `ingest-attachment` * If Tika is not able to parse the document because of a missing class (we are not importing all jars needed by Tika), Tika throws a Throwable which is not catch. This commit removes support for Visio and POTM office files. So elasticsearch is not killed anymore when you run a command like: ``` GET _ingest/pipeline/_simulate { "pipeline" : { "processors" : [ { "attachment" : { "field" : "file" } } ] }, "docs" : [ { "_source" : { "file" : "BASE64CONTENT" } } ] } ``` The good news is that it does not kill the node anymore and allows to extract the text which is in the Office document even if we have a Visio content (which is not extracted anymore). Related to elastic#22077 Backport of elastic#22079 in 5.x branch (5.3)
* Parse a non supported document using `mapper-attachments` * If Tika is not able to parse the document because of a missing class (we are not importing all jars needed by Tika), Tika throws a Throwable which is not catch. This commit removes support for Visio and POTM office files. The good news is that it does not kill the node anymore and allows to extract the text which is in the Office document even if we have a Visio content (which is not extracted anymore). Related to elastic#22077 and elastic#22079 for mapper-attachments plugin
3758b7a
to
64953e3
Compare
Thanks @jasontedor. I rebased and merged. |
* Send a non supported document to an ingest pipeline using `ingest-attachment` * If Tika is not able to parse the document because of a missing class (we are not importing all jars needed by Tika), Tika throws a Throwable which is not catch. This commit removes support for Visio and POTM office files. So elasticsearch is not killed anymore when you run a command like: ``` GET _ingest/pipeline/_simulate { "pipeline" : { "processors" : [ { "attachment" : { "field" : "file" } } ] }, "docs" : [ { "_source" : { "file" : "BASE64CONTENT" } } ] } ``` The good news is that it does not kill the node anymore and allows to extract the text which is in the Office document even if we have a Visio content (which is not extracted anymore). Related to #22077 Backport of #23214 in 5.2 branch
* Parse a non supported document using `mapper-attachments` * If Tika is not able to parse the document because of a missing class (we are not importing all jars needed by Tika), Tika throws a Throwable which is not catch. This commit removes support for Visio and POTM office files. The good news is that it does not kill the node anymore and allows to extract the text which is in the Office document even if we have a Visio content (which is not extracted anymore). Related to #22077 and #22079 for mapper-attachments plugin Backport of #23214 in 5.2 branch
As discussed with @clintongormley, this has been also pushed to 5.2 branch. Related commits: |
I am using Elasticsearch 5.1.2 and facing the same error java.lang.NoClassDefFoundError: com/graphbuilder/curve/Point. |
@dumakant No it won't be backported. You need to upgrade to 5.2.2 which is pretty much straightforward with a rolling upgrade (even easier if you are using elastic cloud). |
I'm running 5.30 and I am receiving this error as a fatal error. Is the fix in the 5.3 release? [2017-04-22T10:54:58,532][ERROR][o.e.b.ElasticsearchUncaughtExceptionHandler] [es-node-docserver] fatal error in thread [elasticsearch[es-node-docserver][bulk][T#9]], exiting |
OMG! I did not push that fix in 5.3 branch apparently. So it's fixed in 5.2, 5.4 but not 5.3... |
@RkirkCBD could you open a new issue and I'll push later today the fix in 5.3 which will go hopefully in 5.3.2? Thanks a lot for reporting ! |
See #24273. Thanks, when should 5.3.2 be released. Is it possible to downgrade my cluster to 5.2.2? |
AFAIK soonish. No you can't downgrade. |
* Send a non supported document to an ingest pipeline using `ingest-attachment` * If Tika is not able to parse the document because of a missing class (we are not importing all jars needed by Tika), Tika throws a Throwable which is not catch. This commit removes support for Visio and POTM office files. So elasticsearch is not killed anymore when you run a command like: ``` GET _ingest/pipeline/_simulate { "pipeline" : { "processors" : [ { "attachment" : { "field" : "file" } } ] }, "docs" : [ { "_source" : { "file" : "BASE64CONTENT" } } ] } ``` The good news is that it does not kill the node anymore and allows to extract the text which is in the Office document even if we have a Visio content (which is not extracted anymore). Related to #22077 Backport of #23214 in 5.3 branch (cherry picked from commit 76a977a)
For the record, I pushed the missing commit in 5.3 as well: dc4888e Apparently I pushed only one of the 2 commits from this PR in the 5.3 branch... :( |
Related to #22077
This PR comes with 2 changes, one for
ingest-attachment
and the other formapper-attachments
.It's essentially a backport of #22079 for 5.x series.
Ingest Attachment Plugin
ingest-attachment
This commit removes support for Visio and POTM office files.
So elasticsearch is not killed anymore when you run a command like:
The good news is that it does not kill the node anymore and allows to extract the text which is in the Office document even if we have a Visio content (which is not extracted anymore).
Mapper Attachments Plugin
mapper-attachments
This commit removes support for Visio and POTM office files.
The good news is that it does not kill the node anymore and allows to extract the text which is in the Office document even if we have a Visio content (which is not extracted anymore).
Note that for this one as we did not apply yet #22963 it hides the fact that we removed the potm sample file from the tika big ZIP file.