[
https://issues.apache.org/jira/browse/GORA-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lewis John McGibbney updated GORA-134:
--
Affects Version/s: 0.2
Fix Version/s: 0.3
ListGenericArray's hashCode
[
https://issues.apache.org/jira/browse/GORA-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278780#comment-13278780
]
Kazuomi Kashii commented on GORA-134:
-
Hi Lewis, I have attached GORA-134-v2.patch with
[
https://issues.apache.org/jira/browse/GORA-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278779#comment-13278779
]
Hudson commented on GORA-95:
Integrated in gora-trunk #280 (See
Hi Ed,
Good to see some interest in pushing things forward.
As the javadoc says, FakeResolvingDecoder is pretty much a big dirty hack
to work around Avro's internals, but as you pointed out much has changed in
Avro, so we may have to rethink those parts.
We need the dirty bits in the
Enis,
Thanks for the pointers. Are the dirty bits only used by Map/Reduce or
for general persistence in terms of application logic? I guess in the
latter case its ok for them to be transient, and if the only other use
case is in Map/Reduce, something could maybe be done in the input and
output
I am all up for not hijacking avro API's :)
Dirty-bits serialization came up first in Hadoop mapreduce, since we have
to serialize the data and the mutation state between tasks. I can think of
other cases, where you may want to serialize object-mutation state, where
you are passing the objects
[
https://issues.apache.org/jira/browse/GORA-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13279396#comment-13279396
]
Renato Javier Marroquín Mogrovejo commented on GORA-135:
I totally
7 matches
Mail list logo
