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 Threaded View
Accumulo >> mail # dev >> SetIterCommand - why set input to new String(input)?


Copy link to this message
-
Re: SetIterCommand - why set input to new String(input)?
Printing a newline to the console reader is probably so the console
appender for the log4j in the shell doesn't print to the same line as
the prompt.

On Tue, Sep 11, 2012 at 4:37 PM, David Medinets
<[EMAIL PROTECTED]> wrote:
> One more question. Why print a newline to the reader if the stream is closed?
>
> On Tue, Sep 11, 2012 at 3:27 PM, Billie Rinaldi <[EMAIL PROTECTED]> wrote:
>> On Tue, Sep 11, 2012 at 11:54 AM, David Medinets
>> <[EMAIL PROTECTED]>wrote:
>>
>>> Is there  some value in the line marked by question marks?
>>>
>>>   private static String setUpOptions(final ConsoleReader reader, final
>>> String className, final Map<String,String> options) ... {
>>>     ...
>>>           if (input == null) {
>>>             reader.printNewline();
>>>             throw new IOException("Input stream closed");
>>>           } else {
>>>             input = new String(input);  <--- ????
>>>           }
>>>   }
>>>
>>
>> That looks like my fault.  I did it twice in the same method.  Can't
>> imagine why.
>>
>> Billie
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