[
https://issues.apache.org/jira/browse/BEAM-6701?focusedWorklogId=199858&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-199858
]
ASF GitHub Bot logged work on BEAM-6701:
----------------------------------------
Author: ASF GitHub Bot
Created on: 17/Feb/19 21:38
Start Date: 17/Feb/19 21:38
Worklog Time Spent: 10m
Work Description: ryan-williams commented on issue #7865: [BEAM-6701] Add
logical types to schema
URL: https://github.com/apache/beam/pull/7865#issuecomment-464509833
btw @reuvenlax where did you get this info?
> It appears that an exception is being throw from
StreamingDataflowWorker.java:1952.
> The following line is failing with NullPointerException:
> `this.transformUserNameToStateFamily =
ImmutableMap.copyOf(transformUserNameToStateFamily);`
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 199858)
Time Spent: 1.5h (was: 1h 20m)
> Create LogicalType for Schema fields
> ------------------------------------
>
> Key: BEAM-6701
> URL: https://issues.apache.org/jira/browse/BEAM-6701
> Project: Beam
> Issue Type: Sub-task
> Components: sdk-java-core
> Reporter: Reuven Lax
> Assignee: Reuven Lax
> Priority: Major
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> This will allow users to create their own logical types to store in schema
> fields, backed by one of the fundamental schema field types. Today SQL hacks
> on top of the field metadata to distinguish its types. LogicalTypes would
> allow for a more principled way of doing this.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
