Non è gestito il commit log quindi un task può essere inserito due volte Per creare questo metodo ho seguito il codice della libreria elasticsearch-spark-20_2.11-6.0.0-rc1-sources.jar -> org.elasticsearch.spark.sql.streaming.EsSparkSqlStreamingSink
Non è gestito il commit log quindi un task può essere inserito due volte Per creare questo metodo ho seguito il codice della libreria elasticsearch-spark-20_2.11-6.0.0-rc1-sources.jar -> org.elasticsearch.spark.sql.streaming.EsSparkSqlStreamingSink
Execute a block of code, then a finally block, but if exceptions happen in the finally block, do not suppress the original exception.
Execute a block of code, then a finally block, but if exceptions happen in the finally block, do not suppress the original exception.
This is primarily an issue with finally { out.close() }
blocks, where
close needs to be called to clean up out
, but if an exception happened
in out.write
, it's likely out
may be corrupted and out.close
will
fail as well. This would then suppress the original/likely more meaningful
exception from the original out.write
call.
Created by Agile Lab s.r.l. on 04/11/2017.