[HIVE-19157] Assert that Insert into Druid Table fails if the publishing of metadata by HS2 fails

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.1.0, 3.0.0
• Assignee: Slim Bouguerra Assign to me
• Reporter: Slim Bouguerra
• Created: 11/Apr/18 00:27
• Updated: 23/May/18 02:16
• Resolved: 14/Apr/18 20:08

Description

The usual work flow of loading Data into Druid relies on the fact that HS2 is able to load Segments metadata from HDFS that are produced by LLAP/TEZ works.
In some cases where HS2 is not able to perform `ls` on the HDFS path the insert into query will return success and will not insert any data.
This bug was introduced at function

 org.apache.hadoop.hive.druid.DruidStorageHandlerUtils#getCreatedSegments

when we added feature to allow create empty tables.

 try {
      fss = fs.listStatus(taskDir);
    } catch (FileNotFoundException e) {
      // This is a CREATE TABLE statement or query executed for CTAS/INSERT
      // did not produce any result. We do not need to do anything, this is
      // expected behavior.
      return publishedSegmentsBuilder.build();
    }

Am still looking for the way to fix this, [~jcamachorodriguez]/Ashutosh Chauhan any idea what is the best way to detect that it is an empty create table statement?

Issue Links

• breaks: HIVE-19194 TestDruidStorageHandler fails
• links to: RB link