Erick Erickson wrote:
>
> 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.
>
entered as SOLR-1782 in jira
--
View this message in context:
http://old.nabble.com/get
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
solr-user wrote:
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
I think they are good for TestCase.
Koji
--
http://www.rondhuit.com/en/
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
: Sure. This is what I get.
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 w
Grant Ingersoll-6 wrote:
>
> Can you share the full output from the StatsComponent?
>
Sure. This is what I get.
-
-
0
62
-
on
*:*
true
ValueOfOne
10
StatsFacetField
StatsFacetField
0
-
-
-
1619
7433
3984
233
41
Can you share the full output from the StatsComponent?
On Feb 15, 2010, at 3:07 PM, solr-user wrote:
>
> Has anyone encountered the following issue?
>
> I wanted to understand the statscomponent better, so I setup a simple test
> index with a few thousand docs. In my schema I have:
> - an
