deletedPkQuery should be usable in full-import as well
--
Key: SOLR-1168
URL: https://issues.apache.org/jira/browse/SOLR-1168
Project: Solr
Issue Type: Improvement
Components: con
[
https://issues.apache.org/jira/browse/SOLR-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar updated SOLR-1129:
Fix Version/s: 1.4
Marking for 1.4 as this is a serious deficiency.
> SolrJ cannot
[
https://issues.apache.org/jira/browse/SOLR-599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar updated SOLR-599:
---
Affects Version/s: (was: 1.3)
Fix Version/s: 1.5
Marking for 1.5
> Lightwe
[
https://issues.apache.org/jira/browse/SOLR-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709350#action_12709350
]
Shalin Shekhar Mangar commented on SOLR-209:
With SOLR-475, is this issue still r
[
https://issues.apache.org/jira/browse/SOLR-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709360#action_12709360
]
Noble Paul commented on SOLR-1129:
--
we released 1.3 w/o it. Still don't have a final patch
[
https://issues.apache.org/jira/browse/SOLR-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709373#action_12709373
]
Avlesh Singh commented on SOLR-1129:
Sorry for the delay. Will submit a patch latest by
On May 13, 2009, at 7:04 PM, Eger, Patrick wrote:
+2
This would be very much appreciated by your users, I at least was
expecting March :-) We were hoping to release with 1.4 (specifically
for
java replication and field collapsing) but had to redo some plans
since
it seemed to keep slippin
The advantage is that there is strength in numbers. There will be a
lot of users using the release build and if there is an issue the user
can rest assured that there will others who need the same fix on the
same revision. (so a better chance of a resolution)
moreover there won't be any half baked
[
https://issues.apache.org/jira/browse/SOLR-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709390#action_12709390
]
Jayson Minard commented on SOLR-1162:
-
UpdateRequest is used on both ends of the stream
[
https://issues.apache.org/jira/browse/SOLR-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709392#action_12709392
]
Noble Paul commented on SOLR-1162:
--
we need a revamp of the JavaBinUpdateRequestCodec .
Th
[
https://issues.apache.org/jira/browse/SOLR-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul reassigned SOLR-1164:
Assignee: Noble Paul
> BinaryUpdateRequestHandler and JavaBinUpdateRequestCodec do not maintain
> o
[
https://issues.apache.org/jira/browse/SOLR-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709394#action_12709394
]
Noble Paul commented on SOLR-1164:
--
I am gonna rewrite JavaBinUpdateRequestCodec to stream
[
https://issues.apache.org/jira/browse/SOLR-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved SOLR-1160.
---
Resolution: Fixed
> AutoCommitTest randomly failed with NullPointerException
> ---
[
https://issues.apache.org/jira/browse/SOLR-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar resolved SOLR-1157.
-
Resolution: Duplicate
Fixed with SOLR-1160.
> Change for timeouts in RequestHandl
[
https://issues.apache.org/jira/browse/SOLR-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12708316#action_12708316
]
Noble Paul edited comment on SOLR-1154 at 5/14/09 7:57 AM:
---
what I
[
https://issues.apache.org/jira/browse/SOLR-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709444#action_12709444
]
Norman Leutner commented on SOLR-773:
-
Hi,
just a comment on the distance function.
{qu
[
https://issues.apache.org/jira/browse/SOLR-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709446#action_12709446
]
Jayson Minard commented on SOLR-1162:
-
Sounds good, didn't like that returned object in
[
https://issues.apache.org/jira/browse/SOLR-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayson Minard updated SOLR-1162:
Attachment: Solr-1162.patch
Updated patch to remove return value from the unmarshall call as suggest
[
https://issues.apache.org/jira/browse/SOLR-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709451#action_12709451
]
Yonik Seeley commented on SOLR-773:
---
bq. if you use a rectangle that does not include any s
Yeah, at least for us, the corporate overlords (and our operations team) would
be *extremely* hesitant to go to production with any kind of snapshot release.
If there was a "weekly stable" or similar that might be slightly better, but
definitely not a CI/nightly.
Best Regards,
Patrick
> ---
[
https://issues.apache.org/jira/browse/SOLR-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709465#action_12709465
]
Noble Paul commented on SOLR-1162:
--
I shall update SOLR-1164 and you can take it over from
> It's not like anything all that magical necessarily happens with a release.
> Sure, we package up the bits and there is some legal ramifications, I
> suppose, but the software is more or less the same. In other words, most
> people should be fine with trunk, or some recent revision. In fact if
[
https://issues.apache.org/jira/browse/SOLR-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709483#action_12709483
]
Henri Biestro commented on SOLR-1154:
-
{quote}
BTW the root of the problem is that there
[
https://issues.apache.org/jira/browse/SOLR-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709484#action_12709484
]
Chris A. Mattmann commented on SOLR-773:
bq. From the user interface point of view, w
After using latest Solr tip I now get errors in Lucene during post-optimize
callbacks that scan the index.
java.lang.IndexOutOfBoundsException: Index: 24, Size: 0
at java.util.ArrayList.RangeCheck(ArrayList.java:547)
at java.util.ArrayList.get(ArrayList.java:322)
at org.ap
[
https://issues.apache.org/jira/browse/SOLR-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709503#action_12709503
]
Jayson Minard commented on SOLR-1162:
-
Sounds good. I'll watch SOLR-1164 for updates.
This is with an optimized index. If I copy it back into the index dir, Solr
opens it up fine and searches it. But the code opening and scanning via
Lucene fails on the same data.
jayson.minard wrote:
>
> After using latest Solr tip I now get errors in Lucene during
> post-optimize callbacks t
Code used is this:
Directory directory = new FSDirectory(new File(luceneIndexDir), null);
reader = IndexReader.open(directory, true); // open directory read-only
...
reader.document(curDoc++, FIELD_SELECTOR);
...
and it bombs on the document() call.
jayson.minard wrote:
>
> This is with an
I'm not suggesting you don't validate it first with your own tests. I
can't imagine you take a release and just deploy it in production,
right?
I'm just observing that if everyone (besides the committers) takes
this "release only" approach, then you quickly realize that the large
majori
[
https://issues.apache.org/jira/browse/SOLR-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709518#action_12709518
]
Yonik Seeley commented on SOLR-:
I just committed the distributed search part of thi
Since Yonik answered over on the Lucene side, continuing this there:
http://www.nabble.com/Getting-errors-reading-lucene-indexes-using-recent-lucene-from-Solr-td23545868.html#a23546172
jayson.minard wrote:
>
> Code used is this:
>
> Directory directory = new FSDirectory(new File(luceneIndexD
FYI, I also planned on starting a discussion about the particular
version and features of Lucene that Solr is using on lucene-dev before
Solr releases.
-Yonik
[
https://issues.apache.org/jira/browse/SOLR-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709571#action_12709571
]
Yonik Seeley commented on SOLR-1166:
Oops, yes, I added a DocSetCollector which doesn't
[
https://issues.apache.org/jira/browse/SOLR-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709578#action_12709578
]
Ryan McKinley commented on SOLR-773:
My apologies for being out of the loop going ba
[
https://issues.apache.org/jira/browse/SOLR-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-1166:
---
Attachment: SOLR-1166.patch
updated patch.
> speed up DocSet generation for term queries and avoid sc
[
https://issues.apache.org/jira/browse/SOLR-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709591#action_12709591
]
Yonik Seeley commented on SOLR-1166:
performance improvement for DocSet generation:
~1
Fair enough, any yes we would definitely do extensive testing before any
release. I think the problem is, that without any "official blessing" I
as a user have no real way of knowing the current state of TRUNK. IE is
some feature in the middle of a rework? Is there some kind of janky
partially-sol
hello everybody
i have to return document from solr only for the latest year. LIke for
example i have 3 documents for 2009 honda accord Coupe bodystyle and two for
2008 honda accord coupe bodystyle. i need to get the latest of results for
make,model,bodyStyle. If i give the query
make:Honda+model
SortedIntDocSet
---
Key: SOLR-1169
URL: https://issues.apache.org/jira/browse/SOLR-1169
Project: Solr
Issue Type: Improvement
Reporter: Yonik Seeley
Assignee: Yonik Seeley
Fix For: 1.4
A Doc
[
https://issues.apache.org/jira/browse/SOLR-1169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709605#action_12709605
]
Yonik Seeley commented on SOLR-1169:
We need skipping in our DocSets in order to be able
[
https://issues.apache.org/jira/browse/SOLR-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved SOLR-1166.
Resolution: Fixed
committed.
> speed up DocSet generation for term queries and avoid scoring for al
[
https://issues.apache.org/jira/browse/SOLR-1169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709645#action_12709645
]
Mike Klaas commented on SOLR-1169:
--
sweet. intersecting sorted int dicts should be faster
Agreed. I think we are all in that boat! Never enough time to do all
the things we want to do.
Cheers,
Grant
On May 14, 2009, at 5:25 PM, Eger, Patrick wrote:
Fair enough, any yes we would definitely do extensive testing before
any
release. I think the problem is, that without any "offic
As a general rule any feature/API from 1.3 that you are using in 1.4
should work on /trunk -- any chances to this are always in CHANGES.txt
The place were you get in to murky water is with new features/API
since the previous release -- in this case, you will need to follow
the JIRA issues t
[
https://issues.apache.org/jira/browse/SOLR-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709684#action_12709684
]
Noble Paul commented on SOLR-1154:
--
I am not referring to SOLR-646 . I mean some easy way t
[
https://issues.apache.org/jira/browse/SOLR-1169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-1169:
---
Attachment: SOLR-1169.patch
Draft patch attached. It's not "hooked in" to Solr yet... just the perfor
[
https://issues.apache.org/jira/browse/SOLR-1169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709713#action_12709713
]
Yonik Seeley commented on SOLR-1169:
The first results are in, and it's looking good.
A
47 matches
Mail list logo
