[
https://issues.apache.org/jira/browse/AVRO-3208?focusedWorklogId=651110&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-651110
]
ASF GitHub Bot logged work on AVRO-3208:
----------------------------------------
Author: ASF GitHub Bot
Created on: 15/Sep/21 14:14
Start Date: 15/Sep/21 14:14
Worklog Time Spent: 10m
Work Description: RyanSkraba opened a new pull request #1339:
URL: https://github.com/apache/avro/pull/1339
Related to https://issues.apache.org/jira/browse/BEAM-12628
It's very common in big data to have a key/value pair where the key is
extracted from a record in the value. This is currently unnecessarily
complicated because if the key is a Utf8 datum that does not implement
Serializable (although it is serializable inside the record itself).
### Jira
- [X] My PR addresses the following [Avro
Jira](https://issues.apache.org/jira/browse/AVRO/) issues and references them
in the PR title. For example, "AVRO-1234: My Avro PR"
- https://issues.apache.org/jira/browse/AVRO-3208
- In case you are adding a dependency, check if the license complies with
the [ASF 3rd Party License
Policy](https://www.apache.org/legal/resolved.html#category-x).
### Tests
- [X] My PR adds the following unit tests : `testSerializable`
### Commits
- [X] My commits all reference Jira issues in their subject lines. In
addition, my commits follow the guidelines from "[How to write a good git
commit message](https://chris.beams.io/posts/git-commit/)":
1. Subject is separated from body by a blank line
1. Subject is limited to 50 characters (not including Jira issue reference)
1. Subject does not end with a period
1. Subject uses the imperative mood ("add", not "adding")
1. Body wraps at 72 characters
1. Body explains "what" and "why", not "how"
### Documentation
- [ ] In case of new functionality, my PR adds documentation that describes
how to use it.
- All the public functions and the classes in the PR contain Javadoc that
explain what it does
--
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]
Issue Time Tracking
-------------------
Worklog Id: (was: 651110)
Remaining Estimate: 0h
Time Spent: 10m
> [Java] Utf8 strings should be Serializable
> ------------------------------------------
>
> Key: AVRO-3208
> URL: https://issues.apache.org/jira/browse/AVRO-3208
> Project: Apache Avro
> Issue Type: New Feature
> Reporter: Ryan Skraba
> Assignee: Ryan Skraba
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It's a common pattern in big data execution engines like Beam, Spark, Flink
> to extract a key from an object and use it in a pipeline for later operations
> on grouping and aggregations. When the Avro string primitive is a Utf8
> datum, this adds unnecessary complexity because it's not serializable.
> This was mostly addressed in AVRO-200 and AVRO-1502 by making generated
> specific Avro objects Serializable or Externalizable, but using a STRING as a
> key is extremely common and worth addressing.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
