Batch Data Load - success but no datasource appearing?

After having gone through the quickstart, I am now trying to get load my own data loaded…

When I run it,

curl -X ‘POST’ -H ‘Content-Type:application/json’ -d @/home/dhopkins/druid-messages-index.json http://localhost:8090/druid/indexer/v1/task

I see in the console success, and in the log I see success…

The bolded line below…looks suspect?..nothing to publish? does this mean…it is not finding any records in the data file?

Is my ISO time stamp format an issue? it doesn’t have milliseconds?

Also I noticed the quickstart example has json fields explicitly when values are null, is that needed?..

i.e. if a column is not present in the data what happens?

if a column is present that is not defined in the spec…what happens?

019-02-04T19:11:20,010 INFO [task-runner-0-priority-0] io.druid.segment.realtime.appenderator.BaseAppenderatorDriver - Pushing segments in background:
2019-02-04T19:11:20,010 INFO [task-runner-0-priority-0] io.druid.segment.realtime.appenderator.AppenderatorImpl - Submitting persist runnable for dataSource[messages_index]
2019-02-04T19:11:20,018 INFO [publish-0] io.druid.segment.realtime.appenderator.BaseAppenderatorDriver - Dropping segments[]
2019-02-04T19:11:20,024 INFO [task-runner-0-priority-0] io.druid.indexing.common.task.IndexTask - Pushed segments[]
2019-02-04T19:11:20,026 INFO [publish-0] io.druid.segment.realtime.appenderator.BaseAppenderatorDriver - Nothing to publish, skipping publish step.
2019-02-04T19:11:20,027 INFO [task-runner-0-priority-0] io.druid.indexing.common.task.IndexTask - Published segments
2019-02-04T19:11:20,027 INFO [task-runner-0-priority-0] io.druid.segment.realtime.appenderator.AppenderatorImpl - Shutting down…
2019-02-04T19:11:20,029 INFO [task-runner-0-priority-0] io.druid.indexing.overlord.TaskRunnerUtils - Task [index_messages_index_2019-02-04T19:10:15.763Z] status changed to [SUCCESS].
2019-02-04T19:11:20,032 INFO [task-runner-0-priority-0] io.druid.indexing.worker.executor.ExecutorLifecycle - Task completed with status: {
“id” : “index_messages_index_2019-02-04T19:10:15.763Z”,
“status” : “SUCCESS”,
“duration” : 308


The ‘druid cluster’ console:

does not show my datasource (it does show the one from the quickstart)

The overlord console…(which shows the tasks/etc)

does in fact show my datasource, and that the task succeeded

Here is my spec:

“spec” : {
“ioConfig” : {
“type” : “index”,
“firehose” : {
“type” : “local”,
“baseDir” : “/home/dhopkins/”,
“filter” : “kafka-file-dump.json”
“appendToExisting” : false
“type” : “index”,
“targetPartitionSize” : 5000000,
“maxRowsInMemory” : 25000,
“forceExtendableShardSpecs” : true


Here is sample data record:

“responseCodeDescription”:“Message delivered”,
“productName”:“111 Way”,



2019-02-04T19:11:20,026 INFO [publish-0] io.druid.segment.realtime.appenderator.BaseAppenderatorDriver - Nothing to publish, skipping publish step.

Your guess is correct. This means there’s no data ingested and thus there’s no segments to create and publish.

If some columns exist in input data but not in the spec, Druid ignores them. If some columns exist in the spec but not in input data, Druid fills those columns with nulls.

I think this is more like a parse error. Can you set logParseExceptions ( to true and see if there’s any parse error?


I updated as follows:

“ioConfig” : {
“type” : “index”,
“firehose” : {
“type” : “local”,
“baseDir” : “/tmp”,
“filter” : “kafka-file-dump.json.gz”
“appendToExisting” : false
“type” : “index”,
“targetPartitionSize” : 4000000,
“maxRowsInMemory” : 25000,
“forceExtendableShardSpecs” : true,


now when I run it…well its odd…I’m not seeing any exceptions/or any new errors

but the odd part is…when I look at the payload/log it doesn’t show the logParseException field…

I know it picking up the changed file…as it is showing the reportParseExceptions as being true, and the targetPartitionSize which I changed from 5xxxx to 4xxxx

ie… it shows:

  "ioConfig" : {
      "type" : "index",
      "firehose" : {
        "type" : "local",
        "baseDir" : "/tmp",
        "filter" : "kafka-file-dump.json.gz",
        "parser" : null
      "appendToExisting" : false
    "tuningConfig" : {
      "type" : "index",
      "targetPartitionSize" : 4000000,
      "maxRowsInMemory" : 25000,
      "maxTotalRows" : 20000000,
      "numShards" : null,
      "indexSpec" : {
        "bitmap" : {
          "type" : "concise"
        "dimensionCompression" : "lz4",
        "metricCompression" : "lz4",
        "longEncoding" : "longs"
      "maxPendingPersists" : 0,
      "buildV9Directly" : true,
      "forceExtendableShardSpecs" : true,
      "forceGuaranteedRollup" : false,
      "reportParseExceptions" : true,
      "pushTimeout" : 0,
      "segmentWriteOutMediumFactory" : null


You can check the ingestion reports of complete tasks via an overlord API (

Would you please check it especially the ‘rowStats’ part?


that yields a 404 :frowning:

Sending a get to:


returns the task json payload


returns 404…

Oh, what druid version are you running?

hrm…0.12.1 - installed via HDP

Ah, yeah. The ingestion reports are available since 0.13.0.

I’m not sure why any rows weren’t ingested. Would you post the task log if possible?


See Attached

tmp.txt (76.8 KB)

Thanks. I see the below log.

2019-02-05T18:29:40,961 INFO [task-runner-0-priority-0] io.druid.segment.realtime.firehose.LocalFirehoseFactory - Initialized with files

This means there’s no input files found. Would you please check it again?


progress :slight_smile: (getting a parse exception atm…looks like I may have truncated row somewhere…will dig into that in a bit).

so the issue was/is (I have this running on a cluster), and switched to doing batch load vs kafka, to validate the payload was good, but…yeah…it decided to run the task on a node where the file wasn’t located…so…my question is…how can one ‘batch’ load a file on a clustered druid…with having to copy the file to all nodes that the task may run on?

and thanx big time for you help :_

indeed last row in the file was truncated…no biggy…but…my question is will this fail the entire load? still not seeing the datasource appear…will try again without the last file.

Ah, if you’re running a cluster, input files should be somewhere where all middleManagers can access to. HDFS, NFS, or AWS S3 are popular options.

After a task is successfully finished, you should wait for a while for a new dataSource to appear. This is because the Druid coordinator periodically refreshes its metadata in memory.