[
https://issues.apache.org/jira/browse/BEAM-5192?focusedWorklogId=582289&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-582289
]
ASF GitHub Bot logged work on BEAM-5192:
----------------------------------------
Author: ASF GitHub Bot
Created on: 14/Apr/21 08:13
Start Date: 14/Apr/21 08:13
Worklog Time Spent: 10m
Work Description: echauchot commented on pull request #10433:
URL: https://github.com/apache/beam/pull/10433#issuecomment-819325068
> > @echauchot
> > I know but it is just a deprecation for now in ES 7.0, types will be
removed later on.
> > For backward compatibility reasons (address indexes created using ES <=
6 we could keep the type. Once the type API is removed (in ES 8.0 I guess), we
could address this breaking change during the migration of the IO. WDYT ?
>
> My $0.02, IMO we should at least remove the log message if we decide to
ignore the deprecation warning, I'm in the middle of refining my logs in
Dataflow and there's no way for me to get rid of those. They keep flooding and
potentially hide other more important ones.
>
> Unless there's a way for ElasticsearchIO to specify which warning not to
print, but I might be missing something! :)
>
> Thank you!
@m4r3x Elasticsearch uses log4j, maybe you could embed a log4j configuration
with your app (and Beam IO) that turns of logging on special ElasticSearch
classes?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 582289)
Time Spent: 4h (was: 3h 50m)
> Support Elasticsearch 7.x
> -------------------------
>
> Key: BEAM-5192
> URL: https://issues.apache.org/jira/browse/BEAM-5192
> Project: Beam
> Issue Type: Improvement
> Components: io-java-elasticsearch
> Reporter: Etienne Chauchot
> Assignee: Etienne Chauchot
> Priority: P2
> Fix For: 2.19.0
>
> Time Spent: 4h
> Remaining Estimate: 0h
>
> ES v7 is not out yet. But Elastic team scheduled a breaking change for ES
> 7.0: the removal of the type feature. See
> [https://www.elastic.co/blog/index-type-parent-child-join-now-future-in-elasticsearch]
> This will require a good amont of changes in the IO.
> This ticket is there to track the future work.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
