SOLR makes heavy use of JUnit for testing. The real advantage of a JUnit testcase being attached is that it can then be permanently incorporated into the SOLR builds. If you're unfamiliar with JUnit, then providing the raw data that illustrates the bug allows people who work on SOLR to save a bunch of time trying to reproduce the problem. It also insures that they are addressing what you're seeing <G>...
It's especially helpful if you can take a bit of time to pare away all the unnecessary stuff in your example files and/or comment what you think the important bits are..... HTH Erick On Wed, Feb 17, 2010 at 5:46 PM, solr-user <solr-u...@hotmail.com> wrote: > > > hossman wrote: > > > > > > That does look really weird, and definitely seems like a bug. > > > > Can you open an issue in Jira? ... ideally with a TestCase (even if it's > > not a JUnit test case, just having some sample docs that can be indexed > > against the example schema and a URL showing the problem would be > helpful) > > > > > > Hossman, what do you mean by including a "TestCase"? > > Will create issue in Jira asap; I will include the URL, schema and some > code > to generate sample data > -- > View this message in context: > http://old.nabble.com/getting-unexpected-statscomponent-values-tp27599248p27631633.html > Sent from the Solr - User mailing list archive at Nabble.com. > >
