Steve,
Thank you for the response. Please see below.
1) Java processing is the rate limiting step. Are you saying Accumulo isn't
designed to run mapreduce ? Can you elaborate please.
I absolutely agree that my implementation should be a chain of map reduce
jobs. Unfortunately, at this time there
A few basic questions -
1) is the rate limiting step the Java processing or storage in accumulo.
Hadoop may not be able to speed up a database which is not designed to work
in a distributed manner.
B) Can ObjectD or any intermediate objects be serialized possibly to xml
and efficiently deseriali
Hello,
Current Design: I have a java object MyObjectA. MyObjectA goes through
Three processors (jars) that are run in sequence and do a lot of processing
to beef up A with tons of additional stuff (think ETL) and the final result
is MyObjectD (note: MyObjectD is really A with more fields if you wi
