Tranquility update now creates Tasks with UTC timestamp instead of PST (problem)

I all!

I just updated my storm topology that uses tranquility to push events in Druid from a really old version: "

com.metamx:tranquility_2.10:0.4.2'"
to a new one: "io.druid:tranquility-storm_2.11:0.7.4" mainly because we want to use Scala 2.11 :)
But we are facing an interesting issue. Before, all the real time tasks were created in Druid using Tranquility with the following names:
"index_realtime_images_impressions_**2016-04-21T18:00:00.000-07:00_0_0**"
now, with the update to tranquility 0.7.4, ids of tasks looks like:
"index_realtime_images_impressions_**2016-04-22T01:00:00.000Z_0_0**"

Suddenly, our task id and names are created following UTC time. This is okay with us ... but apparently not with Tranquility, as we cannot see any data getting inserted in these new tasks... We are completely lost here.

Some interesting logs from our tasks:

        "parseSpec" : {
          "format" : "json",
          "timestampSpec" : {
            "column" : "timestamp",
            "format" : "millis",
            "missingValue" : null
          },

and:

    "ioConfig" : {
      "type" : "realtime",
      "firehose" : {
        "type" : "clipped",
        "delegate" : {
          "type" : "timed",
          "delegate" : {
            "type" : "receiver",
            "serviceName" : "druid:firehose:xxxx-01-0000-0000",
            "bufferSize" : 100000
          },
          "shutoffTime" : "2016-04-22T02:15:00.000Z"
        },
        "interval" : "2016-04-22T01:00:00.000-07:00/2016-04-22T02:00:00.000-07:00"
      }
    },

Any thoughts?

Thanks!

Something’s definitely off there. What version of Druid are you using? Is Druid running with -Duser.timezone=UTC? Tranquility should work in whatever time zone you want to run it in, but Druid itself does require UTC for various reasons.

Hi Gian!

We are using 0.8.1 and Druid is running with UTC timezone. I suspect it must be something with Jackson-joda and joda version itself …

the interval field specified in ioConfig is totally wrong, looks like it did not respect the timezone and just added PST at the end…

"interval" : "2016-04-22T01:00:00.000-07:00/2016-04-22T02:00:00.000-07:00"