Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Plain View
Hadoop >> mail # user >> Re: Writable readFields question


Copy link to this message
-
Re: Writable readFields question
When you're encoding/write()-ing the writable, do you not know the
length? If you do, store the length first, and you can solve your
problem?

On Sat, Aug 24, 2013 at 3:58 AM, Ken Sullivan <[EMAIL PROTECTED]> wrote:
> For my application I'm decoding data in readFields() of non-predetermined
> length.  I've found parsing for "4" (ASCII End Of Transmission) or "-1" tend
> to mark the end of the data stream.  Is this reliable, or is there a better
> way?
>
> Thanks,
> Ken

--
Harsh J
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB