Druid parse error on formatted time field with non-zero timezone

[zhaojiandong]

part of jvm.config:

-Duser.timezone=Asia/Shanghai

timestampSpec config :

"timestampSpec": {
    "format": "yyyy-MM-dd HH:mm:ss",
    "column": "logTime"
}

events example:

{"logTime":"2018-09-10 18:00:00","dim1":"d1","dim2":"d2","value":100}
{"logTime":"2018-09-10 18:00:00","dim1":"d1","dim2":"d2","value":90}

We set user.timezone=Asia/Shanghai, so the correct timestamp is 1536573600000. But druid specifies the UTC timezone, and the TimestampParser recognizes '2018-09-10 18:00:00' as '2018-09-10 18:00:00+00:00' , so it's parsed to 1536602400000.
I will fixed it.

[gianm]

This behavior is intentional: see #6344 (comment) (& also a suggested alternate approach in that same comment).

[stale]

This issue has been marked as stale due to 280 days of inactivity. It will be closed in 2 weeks if no further activity occurs. If this issue is still relevant, please simply write any comment. Even if closed, you can still revive the issue at any time or discuss it on the dev@druid.apache.org list. Thank you for your contributions.

[stale]

This issue has been marked as stale due to 280 days of inactivity. It will be closed in 4 weeks if no further activity occurs. If this issue is still relevant, please simply write any comment. Even if closed, you can still revive the issue at any time or discuss it on the dev@druid.apache.org list. Thank you for your contributions.

[stale]

This issue has been closed due to lack of activity. If you think that is incorrect, or the issue requires additional review, you can revive the issue at any time.