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]
