[BEAM-6052] Fixes bug in ElasticSearchIO for checkForErrors

[Grypse]

@timrobertson100 @echauchot
The checkFor Errors method can not parse the update response before. So i just add the judge logical for partial update, it's a minor bug fix.

The general update response looks like this below:

{
	"took": 293,
	"errors": true,
	"items": [
	{
		"update": {
			"_index": "test_kevin_2018-11",
			"_type": "kevin",
			"_id": "8d7664286c0887c637229166c7c613bc",
			"_version": 1,
			"result": "noop",
			"_shards": {
				"total": 1,
				"successful": 1,
				"failed": 0
			},
			"status": 200
		}
	},				
	{
		"update": {
			"_index": "test_kevin_2018-11",
			"_type": "kevin",
			"_id": "49952be98f4fc160f56bcdb33b1dbf7e",
			"status": 429,
			"error": {
				"type": "es_rejected_execution_exception",
				"reason": "rejected execution of org.elasticsearch.transport.TransportService$7@3f70bbe7 on EsThreadPoolExecutor[name = gjzx159-node2/write, queue capacity = 200, org.elasticsearch.common.util.concurrent.EsThreadPoolExecutor@56b9faa3[Running, pool size = 40, active threads = 40, queued tasks = 200, completed tasks = 10034174]]"
			}
		}
	}
}

So, we need to judge update for update path of jsonnode.

Follow this checklist to help us incorporate your contribution quickly and easily:

• Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.

Post-Commit Tests Status (on master branch)

Lang	SDK	Apex	Dataflow	Flink	Gearpump	Samza	Spark
Go		---	---	---	---	---	---
Java
Python		---			---	---	---

[echauchot]

Thanks for that @Grypse !

• please add tests on the test suite for error parsing in ES2, ES5 and ES6 with partial update mode and full update mode
• comment for later, please rebase on master instead of making a merge commit of the master to your branch.

[echauchot]

@Grypse as I wrote above, you need to rebase your branch on master and not use merge. Right now your PR pushes commits that are already on master. Please re-make your branch:
checkout master
pull --rebase
checkout -b new-branch
and cherry pick your 2 commits on the new branch.
Please also add the tests that I was referring to above.

[Grypse]

OK， It's my first work with open source community. Can u teach me how to do it? Thanks!

…

On Tue, Nov 20, 2018 at 5:54 PM Etienne Chauchot ***@***.***> wrote: @Grypse <https://github.com/Grypse> as I wrote above, you need to rebase your branch on master and not use merge. Right now your PR pushes commits that are already on master. Please re-make your branch: checkout master pull --rebase checkout -b new-branch and cherry pick your 2 commits on the new branch. Please also add the tests that I was referring to above. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#7035 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AI7sPV-asKY6PJLz9ucQHWnEfugPeH0Lks5uw9FlgaJpZM4YdfE9> .

[echauchot]

OK， It's my first work with open source community. Can u teach me how to do it? Thanks!
…
Hi @Grypse,
I already gave you all the procedure in my comment. I adapt it a bit because you work directly on a branch called master:
git checkout -b apache-master apache/master
cherry pick (with Intellij) your 2 commits from master to apache-master
force push apache-master to Grypse:master to update your PR

[echauchot]

closing because replaced by #7206