David Smiley created LUCENE-4574:
Summary: FunctionQuery ValueSource value computed twice per
document
Key: LUCENE-4574
URL: https://issues.apache.org/jira/browse/LUCENE-4574
Project: Lucene - Core
Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-trunk-Linux/2807/
Java: 64bit/jdk1.7.0_09 -XX:+UseParallelGC
All tests passed
Build Log:
[...truncated 23753 lines...]
BUILD FAILED
/mnt/ssd/jenkins/workspace/Lucene-Solr-trunk-Linux/build.xml:62: The following
error occurred while execut
Build: https://builds.apache.org/job/Lucene-Solr-Tests-4.x-Java6/982/
All tests passed
Build Log:
[...truncated 22885 lines...]
BUILD FAILED
/usr/home/hudson/hudson-slave/workspace/Lucene-Solr-Tests-4.x-Java6/build.xml:62:
The following error occurred while executing this line:
/usr/home/hudson/
I'm curious, too. I see some issues with "Lucene fields", one of which is
"Patch", but I don't seem to be able to add that to Radim's issues.
Thanks,
Otis
--
SOLR Performance Monitoring - http://sematext.com/spm/index.html
Search Analytics - http://sematext.com/search-analytics/index.html
On
Build: https://builds.apache.org/job/Lucene-Solr-SmokeRelease-trunk/35/
No tests ran.
Build Log:
[...truncated 30596 lines...]
BUILD FAILED
/usr/home/hudson/hudson-slave/workspace/Lucene-Solr-SmokeRelease-trunk/build.xml:272:
Can't get http://people.apache.org/keys/group/lucene.asc to
/usr/home
can you setup jira to allow set "Patch Available" flag? It does not
seems to allow me on my own tickets
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
I can help too, I don't mean to be just a complainer. Maybe its only a
little more work.
Like i said, that first "patch" i threw up on the issue was just a quick
stab.
Instead of spending a lot of time analyzing what could/couldn't work I just
took a quick stab in the chance that it would be simp
I'm not arguing that it shouldn't be improved. It should. I'll try to take
a look at the tests again.
Shai
On Sat, Nov 24, 2012 at 9:24 PM, Robert Muir wrote:
>
>
> On Sat, Nov 24, 2012 at 11:18 AM, Shai Erera wrote:
>
>> Uwe, it's a good question :). The javadocs aren't that rich, and the
>>
On Sat, Nov 24, 2012 at 11:18 AM, Shai Erera wrote:
> Uwe, it's a good question :). The javadocs aren't that rich, and the
> lucene-facet-examples.jar is created with the source code anyway ...
>
> Robert, I don't know maven enough but I do see this in
> maven/lucene/facet/pom.xml.template:
>
>
Hmmm, I can't seem to get the failure to occur, running lots and lots of
iterations Not quite sure wuat to do next
On Wed, Nov 21, 2012 at 3:51 PM, Mark Miller wrote:
> I'm guessing it's a race of some kind - but I have not had the time to dig
> in yet.
>
> - Mark
>
> On Nov 21, 2012, a
Uwe, it's a good question :). The javadocs aren't that rich, and the
lucene-facet-examples.jar is created with the source code anyway ...
Robert, I don't know maven enough but I do see this in
maven/lucene/facet/pom.xml.template:
${module-path}/src/exam
On Sat, Nov 24, 2012 at 11:05 AM, Shai Erera wrote:
> I don't hack anything, just return things to how they were. If we make the
> separation successfully in time for 4.1, then we can change the build.xml
> back. Otherwise, at least the examples javadocs will be out there.
>
> Since it worked bef
I don't hack anything, just return things to how they were. If we make the
separation successfully in time for 4.1, then we can change the build.xml
back. Otherwise, at least the examples javadocs will be out there.
Since it worked before, I don't think that there will be any issues with
maven, un
The question I have is: why do we need javadocs for the example code? This
makes no sense to me!
Uwe
Robert Muir schrieb:
>On Sat, Nov 24, 2012 at 10:45 AM, Shai Erera wrote:
>
>> It's not that there were failures, but that you moved some tests
>under
>> demo/ that should belong under face
On Sat, Nov 24, 2012 at 10:45 AM, Shai Erera wrote:
> It's not that there were failures, but that you moved some tests under
> demo/ that should belong under facet/. That's the dependency I'm talking
> about. I tried to resolve it, but it wasn't trivial -- either these tests
> will depend on demo
It's not that there were failures, but that you moved some tests under
demo/ that should belong under facet/. That's the dependency I'm talking
about. I tried to resolve it, but it wasn't trivial -- either these tests
will depend on demo/, or we rewrite them to use their own data, which will
take s
On Sat, Nov 24, 2012 at 10:35 AM, Shai Erera wrote:
> You're probably right. The thing is, some facet tests rely on the data
> that exists in the facet examples. The reason is that the examples already
> contain some large number of documents and facets, so it was easy to test
> certain features
You're probably right. The thing is, some facet tests rely on the data that
exists in the facet examples. The reason is that the examples already
contain some large number of documents and facets, so it was easy to test
certain features (I think TotalFacetCounts) with large set of documents,
withou
On Sat, Nov 24, 2012 at 9:18 AM, Shai Erera wrote:
>
> We tried that in LUCENE-3998 without success. The problem are facet tests
> which depend on data that exists in the example package. I don't want to
> disable tests just for the sake of separation, nor move to the examples
> package tests tha
But it is a single module. Yes, it has two artifacts, one of them is
example code.
We can discuss if it needs to be resolved or not (I personally don't think
it's critical). But the current situation is a bug - the examples javadocs
existed and now they're missing.
That's what I want to fix now.
On Sat, Nov 24, 2012 at 9:18 AM, Shai Erera wrote:
> bq. I don't think we should do this.
>
> Why? What's the harm? It's a fairly simple fix to the build.xml and it's
> not like all other modules have example code under demo, such that the
> facet one stands out.
>
>
It makes the build system, pa
bq. I don't think we should do this.
Why? What's the harm? It's a fairly simple fix to the build.xml and it's
not like all other modules have example code under demo, such that the
facet one stands out.
bq. Can we merge these examples into the demo/ module?
We tried that in LUCENE-3998 without s
[
https://issues.apache.org/jira/browse/SOLR-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller reassigned SOLR-2816:
-
Assignee: Yonik Seeley
> Versioning
> --
>
> Key: SOLR-2816
>
[
https://issues.apache.org/jira/browse/SOLR-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved SOLR-2816.
---
Resolution: Fixed
Fix Version/s: (was: 4.1)
4.0
> Versioning
> -
On Sat, Nov 24, 2012 at 2:13 AM, Shai Erera wrote:
> Hi
>
> I noticed that the javadocs for the facet module do not exist in 4.0. In
> the past, the facet/build.xml contains a tag with these packages:
>
>
>
>
> It seems that with the refactoring of the modules-javadocs buil
25 matches
Mail list logo
