[ 
https://issues.apache.org/jira/browse/BEAM-7554?focusedWorklogId=429552&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-429552
 ]

ASF GitHub Bot logged work on BEAM-7554:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 01/May/20 16:43
            Start Date: 01/May/20 16:43
    Worklog Time Spent: 10m 
      Work Description: TheNeuralBit commented on a change in pull request 
#11456:
URL: https://github.com/apache/beam/pull/11456#discussion_r418625619



##########
File path: sdks/java/core/src/main/java/org/apache/beam/sdk/schemas/Schema.java
##########
@@ -419,7 +420,6 @@ public int hashCode() {
     FLOAT,
     DOUBLE,
     STRING, // String.
-    DATETIME, // Date and time.

Review comment:
       Yeah we could deprecate it for a release or two before removing. Would 
we also need to keep support for the primitive DATETIME in IOs and SQL? I'd 
need to think about how that transition would work.




----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 429552)
    Time Spent: 40m  (was: 0.5h)

> datetime and decimal should be logical types
> --------------------------------------------
>
>                 Key: BEAM-7554
>                 URL: https://issues.apache.org/jira/browse/BEAM-7554
>             Project: Beam
>          Issue Type: Improvement
>          Components: dsl-sql, sdk-java-core
>            Reporter: Brian Hulette
>            Priority: Major
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> Currently datetime and decimal are implemented as primitive types in the Java 
> SDK. They should be logical types as documented in 
> https://s.apache.org/beam-schemas



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to