thinkharderdev opened a new issue #2116:
URL: https://github.com/apache/arrow-datafusion/issues/2116
**Describe the bug**
A clear and concise description of what the bug is.
In `datafusion-proto`, `ScalarValue::TimestampX` disregards the optional
timezone:
```rust
datafusion::scalar::ScalarValue::TimestampNanosecond(val, _) => {
create_proto_scalar(val,
PrimitiveScalarType::TimeNanosecond, |s| {
Value::TimeNanosecondValue(*s)
})
}
```
As a result, the value will be deserialized to a
`ScalarValue::TimestampX(<timestamp>,None)`.
This will, for one thing, cause binary expression evaluation to fail if one
operand is a timestamp literal and the other is a column expression for a
column that has a timezone.
**To Reproduce**
Steps to reproduce the behavior:
**Expected behavior**
A clear and concise description of what you expected to happen.
The timestamp should be serialized in the proto message and preserved on
deserialization.
**Additional context**
Add any other context about the problem here.
--
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: github-unsubscr...@arrow.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
