Re: Logic Bug at LogAnalytics.java

2015-08-21 Thread Alfonso Nishikawa
Hi, Furkan. For me it's ok your suggestion, maybe would be ok to maintain something like: if first arg is "help" then show the help although I find much useful show the help if no arg is passed. Anyway, I don't use LogAnalytics, so if the ones who uses that features (including you and if even if

Re: Logic Bug at LogAnalytics.java

2015-08-21 Thread Furkan KAMACI
It is OK for *run* method if you do not pass any data store. It uses default data store for reading and writing. It may be nice to give same behavior to main method. On Fri, Aug 21, 2015 at 6:16 PM, Alfonso Nishikawa < alfonso.nishik...@gmail.com> wrote: > Hi! > I suppose that you can run the Log

Re: Logic Bug at LogAnalytics.java

2015-08-21 Thread Alfonso Nishikawa
Hi! I suppose that you can run the LogAnalytics from other places with mandatory arguments, but if you run it from Main it is mandatory to put 1 argument. I don't find it inherently wrong if you don't consider the only execution being from main. I actually don't use it, so I don't know wether the

Logic Bug at LogAnalytics.java

2015-08-21 Thread Furkan KAMACI
There is a piece of code at LogAnalytics: public static void main(String[] args) throws Exception { if(args.length < 2) { System.err.println(USAGE); System.exit(1); } //run as any other MR job int ret = ToolRunner.run(new LogAnalytics(), args); System.exit(ret); } However at r

[jira] [Created] (GORA-428) Null pointer exception caused by incorrect handling of gora.mongodb.login values that don't validate

2015-08-21 Thread Kevin Findlay (JIRA)
Kevin Findlay created GORA-428: -- Summary: Null pointer exception caused by incorrect handling of gora.mongodb.login values that don't validate Key: GORA-428 URL: https://issues.apache.org/jira/browse/GORA-428