[SPARK-34392][SQL] Support ZoneOffset +h:mm in DateTimeUtils. getZoneId

[Karl-WangSK]

What changes were proposed in this pull request?

To support +8:00 in Spark3 when execute sql
select to_utc_timestamp("2020-02-07 16:00:00", "GMT+8:00")

Why are the changes needed?

+8:00 this format is supported in PostgreSQL,hive, presto, but not supported in Spark3
https://issues.apache.org/jira/browse/SPARK-34392

Does this PR introduce any user-facing change?

no

How was this patch tested?

unit test

[maropu]

ok to test

[maropu]

cc: @MaxGekk

[maropu]

Could you make the PR title clearer? Probably, it should be like [SPARK-34392][SQL] Support a new brabra...

[SparkQA]

Test build #135395 has started for PR 31624 at commit d48a763.

[SparkQA]

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/39975/

[SparkQA]

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/39975/

[SparkQA]

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/39979/

[SparkQA]

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/39979/

[SparkQA]

Test build #135399 has finished for PR 31624 at commit 8b167b3.

• This patch fails Spark unit tests.
• This patch merges cleanly.
• This patch adds no public classes.

[MaxGekk]

Could you just correct/replace by the pattern:

scala> "GMT+8:00".replaceFirst("(\\+|\\-)(\\d)(:|$)", "$10$2$3")
res9: String = GMT+08:00

[Karl-WangSK]

Could you just correct/replace by the pattern:

scala> "GMT+8:00".replaceFirst("(\\+|\\-)(\\d)(:|$)", "$10$2$3")
res9: String = GMT+08:00

yes thx

[SparkQA]

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/40000/

[SparkQA]

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/39999/

[SparkQA]

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/39999/

[SparkQA]

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/40000/

[SparkQA]

Test build #135410 has finished for PR 31624 at commit f3972c9.

• This patch passes all tests.
• This patch merges cleanly.
• This patch adds no public classes.

[SparkQA]

Test build #135419 has finished for PR 31624 at commit eb09f48.

• This patch passes all tests.
• This patch merges cleanly.
• This patch adds no public classes.

[SparkQA]

Test build #135420 has finished for PR 31624 at commit d5e2c1e.

• This patch passes all tests.
• This patch merges cleanly.
• This patch adds no public classes.

[SparkQA]

Test build #135427 has finished for PR 31624 at commit 1e8244f.

• This patch passes all tests.
• This patch merges cleanly.
• This patch adds no public classes.

[SparkQA]

Test build #135458 has finished for PR 31624 at commit 41e0cb0.

• This patch passes all tests.
• This patch merges cleanly.
• This patch adds no public classes.

[srowen]

Merged to master. Do we want this in 3.1?

[maropu]

It seems spark v2.4 supports this syntax, so IMO it would be nice that branch-3.0/3.1 can have this fix, too, for making migrations costs from 2.4 to 3.x smaller. cc: @HyukjinKwon

[yaooqinn]

+1 for 3.1 and 3.0

[srowen]

Done for 3.1. We'll need a different backport for 3.0 as there are merge conflicts - if it is needed in 3.0

[maropu]

@Karl-WangSK Could you open a backport PR for branch-3.0?