[
https://issues.apache.org/jira/browse/GORA-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14048614#comment-14048614
]
Renato Javier Marroquín Mogrovejo commented on GORA-326:
--------------------------------------------------------
Yeah I think we need a bigger clean up with this patch, or a more clever
solution because we don't want to keep on breaking things like what Valerio has
reported.
Hey [~vschiavoni], could you please open a JIRA over in NutchLand so we can
keep track of this bug over there as well?
Thanks I will try to give it a look this week so we can push a new release,
even though this is an improvement and not bug.
> Removal of _g_dirty field from _ALL_FIELDS array and Field Enum in Persistent
> classes
> -------------------------------------------------------------------------------------
>
> Key: GORA-326
> URL: https://issues.apache.org/jira/browse/GORA-326
> Project: Apache Gora
> Issue Type: Improvement
> Components: gora-core
> Affects Versions: 0.4
> Reporter: Alparslan Avcı
> Priority: Minor
> Labels: gora-core
> Fix For: 0.5
>
> Attachments: GORA-326.patch
>
>
> In auto-generated persistent classes, we create an array field called
> ALL_FIELDS as you know. But this array also contains _g_dirty field, which is
> not a stored field at all. Maybe we should remove _g_dirty field from the
> array, since the array is used for getting all fields in the stored table. We
> can also remove it from Field enum, so the users do not know about the
> _g_dirty field.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
