src255 opened a new pull request, #3088:
URL: https://github.com/apache/arrow-rs/pull/3088
# Which issue does this PR close?
<!--
We generally require a GitHub issue to be filed for all bug fixes and
enhancements and this helps us generate change logs for our releases. You can
link an issue to this PR using the GitHub syntax. For example `Closes #123`
indicates that this PR will close issue #123.
-->
Closes #3042
<!--
Why are you proposing this change? If this is already explained clearly in
the issue then this section is not needed.
Explaining clearly why changes are proposed helps reviewers understand your
changes and offer better suggestions for fixes.
-->
# What changes are included in this PR?
<!--
There is no need to duplicate the description in the issue here but it is
sometimes worth providing a summary of the individual changes in this PR.
-->
The `with_timezone_utc` method is implemented with the timezone `"+00:00"`.
Two leading zeros are used for consistency with non-zero offsets. Also, the
signature of `with_timezone` has been changed:
```rust
// pub fn with_timezone(&self, timezone: String) -> Self {/* --snip-- */}
pub fn with_timezone(&self, timezone: impl Into<String>) -> Self {/*
--snip-- */}
```
# Are there any user-facing changes?
<!--
If there are user-facing changes then we may require documentation to be
updated before approving the PR.
-->
The `with_timezone` now accepts `&str` in addition to `String`. For example,
```rust
let arr1: PrimitiveArray<TimestampMillisecondType> =
TimestampMillisecondArray::from(vec![
1546214400000,
-1546214400000,
])
// .with_timezone("+00:00".to_string());
.with_timezone("+00:00");
let arr2: PrimitiveArray<TimestampMillisecondType> =
TimestampMillisecondArray::from(vec![
1546214400000,
-1546214400000,
])
.with_timezone_utc();
assert_eq!(
format!("{:?}", arr1),
format!("{:?}", arr2)
);
```
<!---
If there are any breaking changes to public APIs, please add the `breaking
change` label.
-->
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
