[
https://issues.apache.org/jira/browse/LUCENE-5266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13796481#comment-13796481
]
ASF subversion and git services commented on LUCENE-5266:
-
Commit
[
https://issues.apache.org/jira/browse/SOLR-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Erickson resolved SOLR-5355.
--
Resolution: Invalid
Please move this discussion over to the Solr (or Drupal) user's list. This i
[
https://issues.apache.org/jira/browse/SOLR-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13796404#comment-13796404
]
shruti suri commented on SOLR-5027:
---
Hi,
I am Applying this patch on solr-4.2.1 with bel
[
https://issues.apache.org/jira/browse/SOLR-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13796364#comment-13796364
]
Huynh Viet Tinh edited comment on SOLR-5355 at 10/16/13 3:17 AM:
[
https://issues.apache.org/jira/browse/SOLR-5342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Heisey updated SOLR-5342:
---
Attachment: SOLR-5342.patch
Patch updated with Mark's recommendations. Should I move this to the LUCE
[
https://issues.apache.org/jira/browse/SOLR-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Huynh Viet Tinh updated SOLR-5355:
--
Attachment: solr21.png
solr2.png
solr1.png
3.png
jvm crash.
On Tue, Oct 15, 2013 at 10:57 PM, wrote:
> Build: builds.flonkings.com/job/Lucene-4x-Linux-Java7-64-test-only/122/
>
> All tests passed
>
> Build Log:
> [...truncated 912 lines...]
>[junit4] JVM J4: stdout was not empty, see:
> /var/lib/jenkins/workspace/Lucene-4x-Linux-Java7-64-
Huynh Viet Tinh created SOLR-5355:
-
Summary: Can't index node in drupal 6
Key: SOLR-5355
URL: https://issues.apache.org/jira/browse/SOLR-5355
Project: Solr
Issue Type: Bug
Component
Build: builds.flonkings.com/job/Lucene-4x-Linux-Java7-64-test-only/122/
All tests passed
Build Log:
[...truncated 912 lines...]
[junit4] JVM J4: stdout was not empty, see:
/var/lib/jenkins/workspace/Lucene-4x-Linux-Java7-64-test-only/checkout/lucene/build/core/test/temp/junit4-J4-20131016_045
[
https://issues.apache.org/jira/browse/LUCENE-5286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13796334#comment-13796334
]
Robert Muir commented on LUCENE-5286:
-
FYI: QueryParser documents that its not thread
Jeff Huang created LUCENE-5286:
--
Summary: data races in
org.apache.lucene.queryParser.QueryParserTokenManager
Key: LUCENE-5286
URL: https://issues.apache.org/jira/browse/LUCENE-5286
Project: Lucene - Cor
[
https://issues.apache.org/jira/browse/LUCENE-5266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13796324#comment-13796324
]
ASF subversion and git services commented on LUCENE-5266:
-
Commit
[
https://issues.apache.org/jira/browse/SOLR-5354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13796289#comment-13796289
]
Jessica Cheng commented on SOLR-5354:
-
I think calling indexedToReadable() in QueryComp
[
https://issues.apache.org/jira/browse/SOLR-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13796262#comment-13796262
]
Hoss Man commented on SOLR-5350:
I'm not sure that i understand the problem here.
Solr has
Jessica Cheng created SOLR-5354:
---
Summary: Distributed sort is broken with CUSTOM FieldType
Key: SOLR-5354
URL: https://issues.apache.org/jira/browse/SOLR-5354
Project: Solr
Issue Type: Bug
[
https://issues.apache.org/jira/browse/LUCENE-5266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Ernst updated LUCENE-5266:
---
Fix Version/s: 5.0
4.6
> Optimization of the direct PackedInts readers
>
[
https://issues.apache.org/jira/browse/LUCENE-5266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Ernst reassigned LUCENE-5266:
--
Assignee: Ryan Ernst (was: Adrien Grand)
> Optimization of the direct PackedInts readers
> --
[
https://issues.apache.org/jira/browse/LUCENE-5283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13795553#comment-13795553
]
Dawid Weiss commented on LUCENE-5283:
-
But it can run more than one test? It's more l
> Some of us do not type pefectly!
it'f nefer thoo latte two try!
> Thanks!
Check out the patch, if it's all right then feel free and commit it --
it's getting late and I'm out of office tomorrow so I won't be able to
do it.
Dawid
---
On Tue, Oct 15, 2013 at 2:07 PM, Dawid Weiss
wrote:
> Oh, stop moaning.
:)
> Just be more careful about the filters when you type them ;)
Some of us do not type pefectly!
> I've committed a fix; this will only work from module level -- like I
> said, it may be very tricky to aggregate this acr
[
https://issues.apache.org/jira/browse/LUCENE-5283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13795550#comment-13795550
]
Michael McCandless commented on LUCENE-5283:
Would it be possible to add a ne
I went ahead and pushed it to sonatype. A patch is attached to
kLUCENE-5283. Let me know if this helps anyhow.
Dawid
On Tue, Oct 15, 2013 at 8:07 PM, Dawid Weiss
wrote:
> Oh, stop moaning. Just be more careful about the filters when you type them ;)
>
> I've committed a fix; this will only work
[
https://issues.apache.org/jira/browse/LUCENE-5283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dawid Weiss updated LUCENE-5283:
Attachment: LUCENE-5283.patch
A patch that adds tests.ifNoTests property. Override your defaults t
[
https://issues.apache.org/jira/browse/LUCENE-5283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dawid Weiss updated LUCENE-5283:
Fix Version/s: 5.0
4.6
> Fail the build if ant test didn't execute any tests (e
Nik Everett created LUCENE-5285:
---
Summary: FastVectorHighlighter copies segments scores when
splitting segments across multi-valued fields
Key: LUCENE-5285
URL: https://issues.apache.org/jira/browse/LUCENE-5285
[
https://issues.apache.org/jira/browse/SOLR-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13795488#comment-13795488
]
Chaiyasit (Sit) Manovit commented on SOLR-1634:
---
Hello,
I am not sure if SOL
I'm not very familiar with the distributed sorting code, but based on your
comments, and a quick skim of the functions you pointed to, it definitely
seems like there are two problems here for people trying to implement
custom sorting in custom FieldTypes...
1) QueryComponent.doFieldSortValues
Oh, stop moaning. Just be more careful about the filters when you type them ;)
I've committed a fix; this will only work from module level -- like I
said, it may be very tricky to aggregate this across modules.
https://github.com/carrotsearch/randomizedtesting/commit/78f40f506f933a5ec8dad38e9505f
On 10/15/13 7:33 PM, Shawn Heisey wrote:
On 10/15/2013 8:11 AM, Yonik Seeley wrote:
On Tue, Oct 15, 2013 at 3:46 AM, Per Steffensen
wrote:
Is it deliberate that SolrException.log is not used everywhere in
the code
where we log exceptions (Throwables)? Why? Or is it just by accident?
One prob
On 10/15/2013 8:11 AM, Yonik Seeley wrote:
On Tue, Oct 15, 2013 at 3:46 AM, Per Steffensen wrote:
Is it deliberate that SolrException.log is not used everywhere in the code
where we log exceptions (Throwables)? Why? Or is it just by accident?
One problem with SolrException.log is that the logg
Thanks for getting back to me, Yonik
On 10/15/13 4:11 PM, Yonik Seeley wrote:
On Tue, Oct 15, 2013 at 3:46 AM, Per Steffensen wrote:
Is it deliberate that SolrException.log is not used everywhere in the code
where we log exceptions (Throwables)? Why? Or is it just by accident?
One problem wit
Shalin Shekhar Mangar created SOLR-5353:
---
Summary: Enhance CoreAdmin api to split a route key's documents
from an index
Key: SOLR-5353
URL: https://issues.apache.org/jira/browse/SOLR-5353
Projec
On Tue, Oct 15, 2013 at 11:47 AM, Yonik Seeley wrote:
> On Mon, Oct 14, 2013 at 10:41 AM, Michael McCandless
> wrote:
>> This has actually bit me before too ...
>
> Me too.
> I'm never sure if I may have made a typo... the only way to be sure is
> to tee the output to a file and go back through a
On Mon, Oct 14, 2013 at 10:41 AM, Michael McCandless
wrote:
> This has actually bit me before too ...
Me too.
I'm never sure if I may have made a typo... the only way to be sure is
to tee the output to a file and go back through and look for the test
output.
I've also run things in a loop for an
[
https://issues.apache.org/jira/browse/LUCENE-5109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrien Grand resolved LUCENE-5109.
--
Resolution: Fixed
Fix Version/s: 4.6
Resolved through LUCENE-5236
> EliasFano value in
[
https://issues.apache.org/jira/browse/LUCENE-5236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrien Grand resolved LUCENE-5236.
--
Resolution: Fixed
Fix Version/s: 4.6
Committed. Thanks Paul!
> Use broadword bit selec
[
https://issues.apache.org/jira/browse/LUCENE-5236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13795309#comment-13795309
]
ASF subversion and git services commented on LUCENE-5236:
-
Commit
[
https://issues.apache.org/jira/browse/LUCENE-5236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13795300#comment-13795300
]
ASF subversion and git services commented on LUCENE-5236:
-
Commit
Such things are easier when you don't have junit legacy and all the user
interfaces (eclipse, idea, ant) to take into equation. junit simply assumes
a single jvm model and it needs all test descriptions in advance. There are
other frameworks out there that would be more suitable for forking tests
i
Hi,
ExtendedQueryBase extends the abstract Lucene query class, but you don’t
implement any query-specific method. So Solr does not know which query you want
to execute? The postfilter alone is no valid query.
Also there may be some bugs in your code:
- Where does indexSearcher c
Alessandro Cavallaro created SOLR-5352:
--
Summary: Field name become lowercase in data import handler
Key: SOLR-5352
URL: https://issues.apache.org/jira/browse/SOLR-5352
Project: Solr
Iss
On Tue, Oct 15, 2013 at 3:46 AM, Per Steffensen wrote:
> Is it deliberate that SolrException.log is not used everywhere in the code
> where we log exceptions (Throwables)? Why? Or is it just by accident?
One problem with SolrException.log is that the logger uses that as the
class and method name
Hi, I am developing a post filter implementation in solr 4.2.1 . the
following is a gist to my implementation.
https://gist.github.com/rmuhzin/6991544
I deployed my plugin in the library folder and updated the solrconfig.xml
But when I apply the plugin using
http:/localhost/solr/profiles/sel
Zygmunt Wiercioch created SOLR-5351:
---
Summary: More Like This Handler uses only first field in mlt.fl
when using stream.body
Key: SOLR-5351
URL: https://issues.apache.org/jira/browse/SOLR-5351
Proje
With the Python runner (repeatLuceneTest.py in luceneutil), -iters N
translates into -Dtests.iters=N, while -jvms M translates into running
M JVMs concurrently (for better beasting), so you can combine them to
get lots of beasting.
The runner exits once any of the JVMs hit a failure...
Mike McCan
This is really dangerous: if there is a bug with XYZ codec using this
approach will not find it.
Nor will it find bugs if e.g. the index is constructed in BeforeClass()
I strongly recommend not using this option, i *really* think it should
be removed. This has come up from time to time before.
O
That's what I've seen too -- it picks the master seed once and then all
iters pick their own derivative seeds. So if the test is random at the
before/after/test level, it usually was enough to find bugs after many
iterations.
Shai
On Tue, Oct 15, 2013 at 4:26 PM, Dawid Weiss
wrote:
> >> What do
>> What do you mean? Doesn't it execute the test many times, picking different
>> seeds each time?
Only at the test (method) level, at @Before @After hooks and at @Rule
blocks. @BeforeClass, @AfterClass and class rules are ran with an
identical seed (because you'd have to effectively reload the cl
On Tue, Oct 15, 2013 at 6:20 AM, Shai Erera wrote:
>> please dont use -Dtests.iters! It gives a false sense of security.
>
>
> What do you mean? Doesn't it execute the test many times, picking different
> seeds each time?
>
No it does not!!
---
> please dont use -Dtests.iters! It gives a false sense of security.
Just so that people don't freak out -- what tests.iters does is it
duplicates tests, but the "suite" will only run once. Since
LuceneTestCase picks most random components at the static level
tests.iters=X is really running a one
>
> please dont use -Dtests.iters! It gives a false sense of security.
>
What do you mean? Doesn't it execute the test many times, picking different
seeds each time?
Actually, since I managed to run luceneutil/repeatLuceneTest.py on my
Windows, I almost don't use iters anymore, as repeatLuceneTes
[
https://issues.apache.org/jira/browse/SOLR-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13795167#comment-13795167
]
Joel Bernstein commented on SOLR-5027:
--
Shruti,
I think it should work on 4.2+. Below
Juha Haaga created SOLR-5350:
Summary: Solr 4.5 upgrade instructions don't mention that
solrconfig.xml dataDir variable must now be in another format.
Key: SOLR-5350
URL: https://issues.apache.org/jira/browse/SOLR-535
[
https://issues.apache.org/jira/browse/LUCENE-5272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13795157#comment-13795157
]
ASF subversion and git services commented on LUCENE-5272:
-
Commit
[
https://issues.apache.org/jira/browse/LUCENE-5272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13795155#comment-13795155
]
ASF subversion and git services commented on LUCENE-5272:
-
Commit
[
https://issues.apache.org/jira/browse/SOLR-5349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13795152#comment-13795152
]
Shalin Shekhar Mangar commented on SOLR-5349:
-
Thanks Ricardo!
> CloudSolrServ
[
https://issues.apache.org/jira/browse/SOLR-5349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13795151#comment-13795151
]
ASF subversion and git services commented on SOLR-5349:
---
Commit 15323
[
https://issues.apache.org/jira/browse/SOLR-5349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar resolved SOLR-5349.
-
Resolution: Fixed
Fix Version/s: 5.0
4.5.1
> CloudSolrSe
The test confuses me, it calls bits.ensureCapacity(bit) followed by
bits.fastSet(bit), but if bit becomes the new capacity then it is by
definition out of range?
--
Adrien
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.
[
https://issues.apache.org/jira/browse/SOLR-5349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13795149#comment-13795149
]
ASF subversion and git services commented on SOLR-5349:
---
Commit 15323
[
https://issues.apache.org/jira/browse/SOLR-5349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13795145#comment-13795145
]
ASF subversion and git services commented on SOLR-5349:
---
Commit 15323
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-4.x-Windows/3285/
Java: 32bit/jdk1.8.0-ea-b106 -client -XX:+UseSerialGC
1 tests failed.
REGRESSION: org.apache.lucene.util.TestOpenBitSet.testEnsureCapacity
Error Message:
Stack Trace:
java.lang.AssertionError
at
__randomizedtesting.Se
On Tue, Oct 15, 2013 at 7:38 AM, Shai Erera wrote:
>
> I think it is related but not sure, yet it bugs me. When I want to run same
> method with iterations I need to specify "-Dtests.method=testFoo*
> -Dtests.iters=10". If I just specify testFoo, I get an error. Is it possible
> that the runner w
> I get an error
An error? Or no executed tests? It should be no-matching tests, really.
> Is it possible that the runner will add that '*' for me so that I just
> specify the test method name?
In short no, it's not possible to do so automatically. There is no
such thing as a "method name" in J
>
> Then when you want to rerun your test and limit to that
> particular method you need to glob somehow because these descriptions
> no longer correspond to raw method names
>
I think it is related but not sure, yet it bugs me. When I want to run same
method with iterations I need to specify "-Dt
[
https://issues.apache.org/jira/browse/SOLR-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13795092#comment-13795092
]
Dmitry Kan commented on SOLR-1726:
--
[~sstults] Thanks for the use case. This leans towards
On Tue, Oct 15, 2013 at 6:56 AM, Dawid Weiss
wrote:
>> Hmm, you couldn't just enter the unqualified class name, and then it'd
>> match any package containing that class name? LIke "**/TestFooBar"
>> patternset pattern I think?
>
> This isn't different to your "duplicated test match" scenario. Sam
> Hmm, you couldn't just enter the unqualified class name, and then it'd
> match any package containing that class name? LIke "**/TestFooBar"
> patternset pattern I think?
This isn't different to your "duplicated test match" scenario. Same
class could be present in multiple packages -- what then?
On Tue, Oct 15, 2013 at 4:11 AM, Dawid Weiss
wrote:
>> Is this (the "globbing") really an important feature? Is it somehow
>> necessary in the implementation for other reasons?
>
> There are a few reasons for that:
>
> - without globbing you'd have to provide a fully qualified class name
> (and t
[
https://issues.apache.org/jira/browse/LUCENE-5252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koji Sekiguchi updated LUCENE-5252:
---
Attachment: LUCENE-5252_4x.patch
Fix code regarding one-way synonym (aaa=>bbb).
> add NGram
> Is this (the "globbing") really an important feature? Is it somehow
> necessary in the implementation for other reasons?
There are a few reasons for that:
- without globbing you'd have to provide a fully qualified class name
(and test name);
- Lucene doesn't use it but if we did have one test-
[
https://issues.apache.org/jira/browse/SOLR-5331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13794982#comment-13794982
]
Chris commented on SOLR-5331:
-
I'm not uploading any files to Solr. Only plain text, via SolrIn
Hi
Is it deliberate that SolrException.log is not used everywhere in the
code where we log exceptions (Throwables)? Why? Or is it just by accident?
Regards, Per Steffensen
[
https://issues.apache.org/jira/browse/SOLR-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13794944#comment-13794944
]
shruti suri commented on SOLR-5027:
---
Hi,
Can I apply this patch on solr-4.2.1 version?
74 matches
Mail list logo
