[ https://issues.apache.org/jira/browse/SOLR-5605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13915037#comment-13915037 ]
wolfgang hoschek edited comment on SOLR-5605 at 2/27/14 9:23 PM: ----------------------------------------------------------------- bq. Are you not a committer? At Apache, those who do decide. Yes, but you've clearly been assigned to upstream those contribs and I have plenty of other things to attend to these days. bq. I did not realize Patricks patch did not include the latest code updates from MapReduce. Might be good to pay more attention, also to CDH-14804? bq. I had and still have bigger concerns around the usability of this code in Solr than this issue. It is very, very far from easy for someone to get started with this contrib right now. The usability is fine downstream where maven automatically builds a job jar that includes the necessary dependency jars inside of the lib dir of the MR job jar. Hence no startup script or extra steps are required downstream, just one (fat) jar. If it's not usable upstream it may be because no corresponding packaging system has been used upstream, for reasons that escape me. bq. which is why non of these smaller issues concern me very much at this point. I'm afraid ignorance never helps. was (Author: whoschek): bq. Are you not a committer? At Apache, those who do decide. Yes, but you've clearly been assigned to upstream this stuff and I have plenty of other things to attend to these days. bq. I did not realize Patricks patch did not include the latest code updates from MapReduce. Might be good to pay more attention, also to CDH-14804? bq. I had and still have bigger concerns around the usability of this code in Solr than this issue. It is very, very far from easy for someone to get started with this contrib right now. The usability is fine downstream where maven automatically builds a job jar that includes the necessary dependency jars inside of the lib dir of the MR job jar. Hence no startup script or extra steps are required downstream, just one (fat) jar. If it's not usable upstream it may be because no corresponding packaging system has been used upstream, for reasons that escape me. bq. which is why non of these smaller issues concern me very much at this point. I'm afraid ignorance never helps. > MapReduceIndexerTool fails in some locales -- seen in random failures of > MapReduceIndexerToolArgumentParserTest > --------------------------------------------------------------------------------------------------------------- > > Key: SOLR-5605 > URL: https://issues.apache.org/jira/browse/SOLR-5605 > Project: Solr > Issue Type: Bug > Reporter: Hoss Man > Assignee: Mark Miller > Fix For: 4.7, 5.0 > > > I noticed a randomized failure in MapReduceIndexerToolArgumentParserTest > which is reproducible with any seed -- all that matters is the locale. > The problem sounded familiar, and a quick search verified that jenkins has in > fact hit this a couple of times in the past -- Uwe commented on the list that > this is due to a real problem in one of the third-party dependencies (that > does the argument parsing) that will affect usage on some systems. > If working around the bug in the arg parsing lib isn't feasible, > MapReduceIndexerTool should fail cleanly if the locale isn't one we know is > "supported" -- This message was sent by Atlassian JIRA (v6.1.5#6160) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org