[ 
https://issues.apache.org/jira/browse/BEAM-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Scott Wegner updated BEAM-134:
------------------------------
    Description: 
The initial PR for [BEAM-118] added a dependency on 
[AutoValue|https://github.com/google/auto/tree/master/value#how-to-use-autovalue]
 to auto-implement equality semantics for a new POJO. We decided to remove the 
dependency because the cost of adding the dependency for this feature may not 
be worth it for the value.

However, we could use AutoValue for all of our POJO's, it might be worth it. 
The proposal here is to follow-up with an investigation on whether we would 
gain significant value to porting our code to use AutoValue instead of 
hand-written POJO's.

  was:
The initial PR for [BEAM-118] added a dependency on AutoValue to auto-implement 
equality semantics for a new POJO. We decided to remove the dependency because 
the cost of adding the dependency for this feature may not be worth it for the 
value.

However, we could use AutoValue for all of our POJO's, it might be worth it. 
The proposal here is to follow-up with an investigation on whether we would 
gain significant value to porting our code to use AutoValue instead of 
hand-written POJO's.


> Investigate use of AutoValue
> ----------------------------
>
>                 Key: BEAM-134
>                 URL: https://issues.apache.org/jira/browse/BEAM-134
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-java-core
>            Reporter: Scott Wegner
>            Assignee: Scott Wegner
>            Priority: Minor
>         Attachments: 
> 0001-Mark-classes-which-might-benefit-from-AutoValue.patch
>
>
> The initial PR for [BEAM-118] added a dependency on 
> [AutoValue|https://github.com/google/auto/tree/master/value#how-to-use-autovalue]
>  to auto-implement equality semantics for a new POJO. We decided to remove 
> the dependency because the cost of adding the dependency for this feature may 
> not be worth it for the value.
> However, we could use AutoValue for all of our POJO's, it might be worth it. 
> The proposal here is to follow-up with an investigation on whether we would 
> gain significant value to porting our code to use AutoValue instead of 
> hand-written POJO's.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to