Hi,
What is the query or code that you are using when you encounter the error?
Regards,
Edwin
On Thu, 9 May 2019 at 10:36, Aroop Ganguly wrote:
>
>
> Hi
>
> I am on Solr 7.5 and I am issuing a delete-by-query using CloudSolrClient
> The collection exists but issuing a delete
Hi
I am on Solr 7.5 and I am issuing a delete-by-query using CloudSolrClient
The collection exists but issuing a deletebyquery is failing every single time.
I am wondering what is happening, and how to debug this.
org.apache.solr.client.solrj.SolrServerException
e using the default solrconfig values and the autoCommit and softCommits
> are set to 5 minutes. The SOLR cluster is supported by 3 ZK.
> We are able to reach 5000/s updates and we are using solrj to index the data
> to solr. We also delete the documents in each of the collection periodically
d the autoCommit and softCommits are set
to 5 minutes. The SOLR cluster is supported by 3 ZK.
We are able to reach 5000/s updates and we are using solrj to index the data to
solr. We also delete the documents in each of the collection periodically using
solrj delete by query method(we use a non-id fil
Hi Emir,
We are deleting a larger subset of docs with a particular value which we
know based on the id and only updating a few of the deleted. Our document
is of the form
__, we need to delete all that has the same ,
that are no longer in DB and then update only a few that has been updated
in DB.
Hi Sujatha,
Did I get it right that you are deleting the same documents that will be
updated afterward? If that’s the case, then you can simply skip deleting, and
just send updated version of document. Solr (Lucene) does not have delete -
it’ll just flag document as deleted. Updating document (a
Thanks,Shawn.
Our use case is something like this in a batch load of several 1000's of
documents,we do a delete first followed by update.Example delete all 1000
docs and send an update request for 1000.
What we see is that there are many missing docs due to DBQ re-ordering of
the order of delet
On 6/21/2018 9:59 AM, sujatha sankaran wrote:
> Currently from our business perspective we find that we are left with no
> options for deleting docs in a batch load as :
>
> DBQ+ batch does not work well together
> DBI+ custom routing (batch load / normal)would not work as well.
I would expect
Thanks,Shawn.
Currently from our business perspective we find that we are left with no
options for deleting docs in a batch load as :
DBQ+ batch does not work well together
DBI+ custom routing (batch load / normal)would not work as well.
We are not sure how we can proceed unless we don't hav
On 6/20/2018 3:46 PM, sujatha sankaran wrote:
> Thanks,Shawn. Very useful information.
>
> Please find below the log details:-
Is your collection using the implicit router? You didn't say. If it
is, then I think you may not be able to use deleteById. This is indeed
a bug, one that has been re
Thanks,Shawn. Very useful information.
Please find below the log details:-
2018-06-20 17:19:06.661 ERROR
(updateExecutor-2-thread-8226-processing-crm_v2_01_shard3_replica1
x:crm_v2_01_shard3_replica2 r:core_node4 n:masked:8983_solr s:shard3
c:crm_v2_01) [c:crm_v2_01 s:shard3 r:core_node4
x:cr
On 6/15/2018 3:14 PM, sujatha sankaran wrote:
We were initially having an issue with DBQ and heavy batch updates which
used to result in many missing updates.
After reading many mails in mailing list which mentions that DBQ and batch
update do not work well together, we switched to DBI. But we
We were initially having an issue with DBQ and heavy batch updates which
used to result in many missing updates.
After reading many mails in mailing list which mentions that DBQ and batch
update do not work well together, we switched to DBI. But we are seeing
issue as mentioned in this jira is
Thanks Erick,
The *'s were accidental, if that makes any difference whatsoever.
On 09/04/16 15:42, Erick Erickson wrote:
Should work, or
-merchant_id:(12345 OR 9876*)
But do be aware that Solr is not strict boolean logic. The above is
close enough for this purpose. Here's an excellent write
Should work, or
-merchant_id:(12345 OR 9876*)
But do be aware that Solr is not strict boolean logic. The above is
close enough for this purpose. Here's an excellent writeup on this
subtlety:
https://lucidworks.com/blog/2011/12/28/why-not-and-or-and-not/
Best,
Erick
On Sat, Apr 9, 2016 at 3:51 A
Hi,
I have this delete query: "*partner:pg AND market:us AND last_seen:[* TO
2016-04-09T02:01:06Z]*"
And would like to add "AND merchant_id != 12345 AND merchant_id != 98765"
Would this be done by including "*AND -merchant_id:12345 AND
-merchant_id:98765*" ?
Thanks,
Rob
Ouch! I certainly did not mean to sound snippy. But perhaps it did, at
least to some people. I'll try to be even more PC in the future.
I am glad the problem was resolved in the end.
Newsletter and resources for Solr beginners and intermediates:
http://www.solr-start.com/
On 23 March 2016 a
On Tue, Mar 22, 2016 at 10:25:06PM -0400, Jack Krupansky wrote:
> See the correct syntax example here:
> https://cwiki.apache.org/confluence/display/solr/Uploading+Data+with+Index+Handlers#UploadingDatawithIndexHandlers-SendingJSONUpdateCommands
>
> Your query is fine.
Thanks; I thought the query
On Tue, Mar 22, 2016 at 04:27:03PM -0700, Walter Underwood wrote:
> “Why do you care?” might not be the best way to say it, but it is
> essential to understand the difference between selection (filtering)
> and ranking.
>
> As Solr params:
>
> * q is ranking and filtering
> * fq is filtering on
See the correct syntax example here:
https://cwiki.apache.org/confluence/display/solr/Uploading+Data+with+Index+Handlers#UploadingDatawithIndexHandlers-SendingJSONUpdateCommands
Your query is fine.
-- Jack Krupansky
On Tue, Mar 22, 2016 at 3:07 PM, Paul Hoffman wrote:
> I've been struggling to
“Why do you care?” might not be the best way to say it, but it is essential to
understand the difference between selection (filtering) and ranking.
As Solr params:
* q is ranking and filtering
* fq is filtering only
* bq is ranking only
When deleting documents, ordering does not matter, which i
"why do you care? just do this ..."
I see this a lot on mailing lists these days, it's usually a learning
curve/task/question. I know I fall into these types of questions/tasks
regularly.
Which usually leads to "don't tell me my approach is wrong, just explain
what's going on, and why", or
Why do you care?
The difference between Q and FQ are the scoring. For delete, you
delete all of them regardless of scoring and there is no difference.
Just chuck them all into Q.
Regards,
Alex.
Newsletter and resources for Solr beginners and intermediates:
http://www.solr-start.com/
On
I've been struggling to find the right syntax for deleting by query
using JSON, where the query includes an fq parameter.
I know how to delete *all* documents, but how would I delete only
documents with field doctype = "cres"? I have tried the following along
with a number of variations, all t
Instead of using SolrQuery to make a query request, you can use the
UpdateRequest class. Something like the following should do the same
as your intended request:
CloudSolrClient solr = new
CloudSolrClient("127.0.0.1:2181,127.0.0.2:2181, 127.0.0.3:218/solr1");
solr.setIdField("cust");
solr.setDefa
Is it possible to execute the following via CloudSolrClient? It works via
curl.
curl
'http://localhost:8983/solr/asset/update/json?_route_="b!"&json.filter="cust:b";'
-H 'Content-type:application/json' -d
'{params:{},"delete":{"query":"cust:b"},"commit": {},"optimize": {}}'
I've tried the fol
.
I mean to ask: is there any solr admin meta data I can fetch through restful
api, to get data such as index last updated time, or something like that?
--
View this message in context:
http://lucene.472066.n3.nabble.com/is-there-any-way-to-tell-delete-by-query-actually-deleted-anything
On 9/2/2015 3:32 PM, Renee Sun wrote:
> I think we have similar structure where we use frontier/back instead of
> hot/cold :-)
>
> so yes we will probably have to do the same.
>
> since we have large customers and some of them may have tera bytes data and
> end up with hundreds of cold cores th
Hi Erick... as Shawn pointed out... I am not using solrcloud, I am using a
more complicated sharding scheme, home grown...
thanks for your response :-)
Renee
--
View this message in context:
http://lucene.472066.n3.nabble.com/is-there-any-way-to-tell-delete-by-query-actually-deleted-anything
-delete-by-query-actually-deleted-anything-tp4226776p4226805.html
Sent from the Solr - User mailing list archive at Nabble.com.
On 9/2/2015 2:24 PM, Renee Sun wrote:
> I have a sharded index. When I re-index a document (vs new index, which is
> different process), I need to delete the old one first to avoid dup. We all
> know that if there is only one core, the newly added document will replace
> the old one, but with multi
> I could alternatively use query first and skip if it did not hit, but delete
> if it does, and I can't short circuit since we have dups :-( based on a
> historical reason.
>
> any suggestion how to make this more efficiently?
>
> thanks!
>
>
>
>
>
>
x27;t short circuit since we have dups :-( based on a
historical reason.
any suggestion how to make this more efficiently?
thanks!
--
View this message in context:
http://lucene.472066.n3.nabble.com/is-there-any-way-to-tell-delete-by-query-actually-deleted-anything-tp4226776p4226788.html
Sent
On 9/2/2015 1:30 PM, Renee Sun wrote:
> Is there an easy way for me to get the actually deleted document number? I
> mean if the query did not hit any documents, I want to know that nothing got
> deleted. But if it did hit documents, i would like to know how many were
> delete...
I do this by issu
ument number? I
> mean if the query did not hit any documents, I want to know that nothing
> got
> deleted. But if it did hit documents, i would like to know how many were
> delete...
>
> thanks
> Renee
>
>
>
> --
> View this message in context:
> http://l
bble.com/is-there-any-way-to-tell-delete-by-query-actually-deleted-anything-tp4226776.html
Sent from the Solr - User mailing list archive at Nabble.com.
Shawn, thank you very much for that explanation. It helps a lot.
Cheers, Ryan
On Wed, May 20, 2015 at 5:07 PM, Shawn Heisey wrote:
> On 5/20/2015 5:57 PM, Ryan Cutter wrote:
> > GC is operating the way I think it should but I am lacking memory. I am
> > just surprised because indexing is perf
On 5/20/2015 5:57 PM, Ryan Cutter wrote:
> GC is operating the way I think it should but I am lacking memory. I am
> just surprised because indexing is performing fine (documents going in) but
> deletions are really bad (documents coming out).
>
> Is it possible these deletes are hitting many seg
GC is operating the way I think it should but I am lacking memory. I am
just surprised because indexing is performing fine (documents going in) but
deletions are really bad (documents coming out).
Is it possible these deletes are hitting many segments, each of which I
assume must be re-built? An
On 5/20/2015 5:41 PM, Ryan Cutter wrote:
> I have a collection with 1 billion documents and I want to delete 500 of
> them. The collection has a dozen shards and a couple replicas. Using Solr
> 4.4.
>
> Sent the delete query via HTTP:
>
> http://hostname:8983/solr/my_collection/update?stream.bo
I have a collection with 1 billion documents and I want to delete 500 of
them. The collection has a dozen shards and a couple replicas. Using Solr
4.4.
Sent the delete query via HTTP:
http://hostname:8983/solr/my_collection/update?stream.body=
source:foo
Took a couple minutes and several repli
: Monday, February 2, 2015 11:44 PM
To: solr-user@lucene.apache.org
Subject: Re: Delete By query on a multi-value field
Hi Jean,
Please see the issues
https://issues.apache.org/jira/browse/SOLR-3862
https://issues.apache.org/jira/browse/SOLR-5992
Both of them are resolved. The *remove *clause
",
> "2,3,4" and "1". I'd like to remove anything that has the value '1' in the
> field XYZ. That is I want to remove the value '1' from the field, deleting
> the document only if '1' is the only value present.
>
>
>
ld XYZ. That is I want to remove the value '1' from the field, deleting the
document only if '1' is the only value present.
Deleting documents such as C (single value) is easy with a Delete by query
through the update handler but what about document A?
Thanks for any hint
Hi Jess;
Could you check here first:
http://search-lucene.com/m/QTPaSxpsW/Commit+Within+and+%252Fupdate%252Fextract+handler&subj=Re+Commit+Within+and+update+extract+handler
and
then here:
http://searchhub.org/2013/08/23/understanding-transaction-logs-softcommit-and-commit-in-sorlcloud/
Thanks;
Fu
It appears that UpdateResponse.setCommitWithin is not honored when executing a
delete query against SolrCloud (SolrJ 4.6). However, setting the hard commit
parameter functions as expected. Is this a known bug?
Thanks,
-Jess
013, at 1:53 PM, Brett Hoerner
>>>>> wrote:
>>>>>>>
>>>>>>>> Here is a dump after the delete, indexing has been stopped:
>>>>>>>> https://gist.github.com/bretthoerner/c7ea3bf3dc9e676a3f0e
>>>>>>>>
>>>>
hint that I forgot to mention: it doesn't always
>> happen
>> >> on
>> >>>>> the first delete. I manually ran the delete cron, and the server
>> >>>> continued
>> >>>>> to work. I waited about 5 minutes and ran it again and
No, not a poor idea at all, definitely a valid setup.
- Mark
On Mar 7, 2013, at 9:30 AM, Brett Hoerner wrote:
> As a side note, do you think that was a poor idea? I figured it's better to
> spread the master "load" around?
>
>
> On Thu, Mar 7, 2013 at 11:29 AM, Mark Miller wrote:
>
>>
>> O
As a side note, do you think that was a poor idea? I figured it's better to
spread the master "load" around?
On Thu, Mar 7, 2013 at 11:29 AM, Mark Miller wrote:
>
> On Mar 7, 2013, at 9:03 AM, Brett Hoerner wrote:
>
> > To be clear, neither is really "the replica", I have 32 shards and each
>
On Mar 7, 2013, at 9:03 AM, Brett Hoerner wrote:
> To be clear, neither is really "the replica", I have 32 shards and each
> physical server is the leader for 16, and the replica for 16.
Ah, interesting. That actually could be part of the issue - some brain cells
are firing. I'm away from home
about 5 minutes and ran it again and it stalled the
> >>>>> indexer (as seen from indexer process):
> http://i.imgur.com/1Tt35u0.png
> >>>>>
> >>>>> Another thing I forgot to mention. To bring the cluster back to life
> I:
> >>>
start start2
>>>>> 4) manually rebalance half of the shards to be mastered on server2
>>>>> (unload/create on server1)
>>>>> 5) restart indexer
>>>>>
>>>>> And it works again until a delete eventually kills it.
>>>&
>>> And it works again until a delete eventually kills it.
> >>>
> >>> To be clear again, select queries continue to work indefinitely.
> >>>
> >>> Thanks,
> >>> Brett
> >>>
> >>>
> >>> On Wed, M
clear again, select queries continue to work indefinitely.
>>>
>>> Thanks,
>>> Brett
>>>
>>>
>>> On Wed, Mar 6, 2013 at 1:50 PM, Mark Miller
>> wrote:
>>>
>>>> Which version of Solr?
>>>>
>>>
gt; >>
> >> Can you use jconsole, visualvm, or jstack to get some stack traces and
> see
> >> where things are halting?
> >>
> >> - Mark
> >>
> >> On Mar 6, 2013, at 11:45 AM, Brett Hoerner
> wrote:
> >>
> >>> I have a
s, 32 shards,
>>> replication factor of 2) that I've been using for over a month now in
>>> production.
>>>
>>> Suddenly, the hourly cron I run that dispatches a delete by query
>>> completely halts all indexing. Select queries still run (and quickly),
>
cation factor of 2) that I've been using for over a month now in
> > production.
> >
> > Suddenly, the hourly cron I run that dispatches a delete by query
> > completely halts all indexing. Select queries still run (and quickly),
> > there is no CPU or disk I/O happ
1:45 AM, Brett Hoerner wrote:
>
> > I have a SolrCloud cluster (2 machines, 2 Solr instances, 32 shards,
> > replication factor of 2) that I've been using for over a month now in
> > production.
> >
> > Suddenly, the hourly cron I run that dispatches a delete by que
t I've been using for over a month now in
> production.
>
> Suddenly, the hourly cron I run that dispatches a delete by query
> completely halts all indexing. Select queries still run (and quickly),
> there is no CPU or disk I/O happening, but suddenly my indexer (which runs
> a
I have a SolrCloud cluster (2 machines, 2 Solr instances, 32 shards,
replication factor of 2) that I've been using for over a month now in
production.
Suddenly, the hourly cron I run that dispatches a delete by query
completely halts all indexing. Select queries still run (and quickly),
the
tent-Type:
text/xml" --data-binary '
id:doc-2012-12-18'
-- Jack Krupansky
-Original Message- From: Dixline
Sent: Tuesday, December 18, 2012 1:03 AM
To: solr-user@lucene.apache.org
Subject: Delete by Query not working properly
Hi,
I've deleted a document using
http:
ot;Content-Type:
> text/xml" --data-binary '
> id:doc-2012-12-18'
>
> -- Jack Krupansky
>
> -Original Message- From: Dixline
> Sent: Tuesday, December 18, 2012 1:03 AM
> To: solr-user@lucene.apache.org
> Subject: Delete by Query not working properly
ecember 18, 2012 9:03 AM
To: solr-user@lucene.apache.org
Subject: Re: Delete by Query not working properly
Make sure that your curl command includes:
-H "Content-Type: text/xml"
For example,
curl http://localhost:8983/solr/update?commit=true -H "Content-Type:
text/xml" --d
ne
Sent: Tuesday, December 18, 2012 1:03 AM
To: solr-user@lucene.apache.org
Subject: Delete by Query not working properly
Hi,
I've deleted a document using http://localhost:8983/solr/update?stream.body=
skills_s:Perl and the committed the delete
also. Again if search using q=perl i'm able
able to see the same document but
> if
> i search using q=skills_s:Perl it is not returning any results. Can
> someone
> explain is this how delete by query works?
>
> Thanks,
> Dixline.M
>
>
>
> --
> View this message in context:
> http://lucene.47206
s this how delete by query works?
Thanks,
Dixline.M
--
View this message in context:
http://lucene.472066.n3.nabble.com/Delete-by-Query-not-working-properly-tp4027681.html
Sent from the Solr - User mailing list archive at Nabble.com.
Sorry, I had copy/paste the wrong link before. Here is the correct one:
https://issues.apache.org/jira/browse/SOLR-3986
Bill
On Wed, Oct 24, 2012 at 10:26 AM, Bill Au wrote:
> I just filed a bug with all the details:
>
> https://issues.apache.org/jira/browse/SOLR-3681
>
> Bill
>
>
> On Tue, O
I just filed a bug with all the details:
https://issues.apache.org/jira/browse/SOLR-3681
Bill
On Tue, Oct 23, 2012 at 2:47 PM, Chris Hostetter
wrote:
> : Just discovered that the replication admin REST API reports the correct
> : index version and generation:
> :
> : http://master_host:port/sol
: Just discovered that the replication admin REST API reports the correct
: index version and generation:
:
: http://master_host:port/solr/replication?command=indexversion
:
: So is this a bug in the admin UI?
Ya gotta be specific Bill: where in the admin UI do you think it's
displaying the inc
page also shows the older index version and generation for the master.
If I do a second delete by query on the master, the master index generation
reported the admin UI does go up by one on both the master and slave. But
it is still one generation behind.
Bill
On Fri, Oct 19, 2012 at 7:09 AM,
ill
>
> On Thu, Oct 18, 2012 at 11:34 AM, Bill Au wrote:
>
>> I just upgraded to Solr 4.0.0. I noticed that after a delete by query,
>> the index version, generation, and size remain unchanged on the master even
>> though the documents have been deleted (num docs chan
I noticed that after a delete by query,
> the index version, generation, and size remain unchanged on the master even
> though the documents have been deleted (num docs changed and those deleted
> documents no longer show up in query responses). But on the slave both the
> index version,
I just upgraded to Solr 4.0.0. I noticed that after a delete by query, the
index version, generation, and size remain unchanged on the master even
though the documents have been deleted (num docs changed and those deleted
documents no longer show up in query responses). But on the slave both the
> Do you have a "_version_" field in
> your schema. I believe SOLR 4.0
> Beta requires that field.
Probably he is hitting this https://issues.apache.org/jira/browse/SOLR-3432
Do you have a "_version_" field in your schema. I believe SOLR 4.0
Beta requires that field.
Ravi Kiran Bhaskar
On Wed, Oct 10, 2012 at 11:45 AM, Andrew Groh wrote:
> I cannot seem to get delete by query working in my simple setup in Solr 4.0
> beta.
>
> I have a single
I cannot seem to get delete by query working in my simple setup in Solr 4.0
beta.
I have a single collection and I want to delete old documents from it. There
is a single solr node in the config (no replication, not distributed). This is
something that I previously did in Solr 3.x
My
indivisual document
solr.Delete(new SolrQueryByField("id", "SP2514N"));
Here particular id="SP2514N" will be removed from the Indexed data.
--
View this message in context:
http://lucene.472066.n3.nabble.com/delete-by-query-don-t-work-tp3990077p3990243.html
Sent from the Solr - User mailing list archive at Nabble.com.
On Mon, 2012-06-18 at 11:45 +0200, ramzesua wrote:
> Hi all. I am using solr 4.0 and trying to clear index by query. At first I
> use *:* with commit, but index is still not
> empty. I tried another queries, but it not help me. Then I tried delete by
> `id`. It works fine, but I need clear all inde
Well, it would help if you defined what behavior you're seeing. When you
say delete-by-query doesn't work, what is the symptom? What does "empty"
mean? Because if you're just looking at your index directory and expecting
to see files disappear, you'll be disappointed.
:
http://lucene.472066.n3.nabble.com/delete-by-query-don-t-work-tp3990077.html
Sent from the Solr - User mailing list archive at Nabble.com.
core.
- I do now also have a backup of my data in mysql
Thank you very much for your help!
--
View this message in context:
http://lucene.472066.n3.nabble.com/Delete-by-Query-with-limited-number-of-rows-tp3503094p3506380.html
Sent from the Solr - User mailing list archive at Nabble.com.
There's nothing built into Solr that lets you do this automatically. About
the best you can do is probably a delete by query going back some fixed
time interval. So rather than keeping the last N documents, you keep
documents that are, say, no more than 1 month old (or whatever you
determine
ly automatically increase it's value
for each added (commited) document? So that I could use a placeholder like
"NOW" in the case of the DateField to indicate that I would like to
auto-increment the field.
Cheers
Michael
--
View this message in context:
http://lucene.472066.n3.nabb
On 11/12/2011 4:08 PM, mikr00 wrote:
> Similar to a first in first out list. The problem is: It's easy to check the
> limit, but how can I delete the oldest documents to go again below the
> limit? Can I do it with a delete by query request? In that case, I would
> probably
no longer exceeded.
Similar to a first in first out list. The problem is: It's easy to check the
limit, but how can I delete the oldest documents to go again below the
limit? Can I do it with a delete by query request? In that case, I would
probably have to limit the number of rows? But I can'
i resolved:
http://10.0.0.178:8983/solr/update?stream.body=
(field1:value1)AND(field2:value2)
Thanx
2011/3/28 Gastone Penzo
> Hi,
> i want to use delete by query method to delete indexes.
> i try for example:
>
> http://10.0.0.178:8983/solr/update?stream.body=
> field1:valu
Hi,
i want to use delete by query method to delete indexes.
i try for example:
http://10.0.0.178:8983/solr/update?stream.body=
field1:value
and it works
but how can delete indexes by 2 filters?
http://10.0.0.178:8983/solr/update?stream.body=field1:value1
AND field2:value2
it doesn't wo
terms wont
get refreshed unless you optimize your index..
Thanks,
Barani
--
View this message in context:
http://lucene.472066.n3.nabble.com/Delete-by-query-or-Id-very-slow-tp2053699p2067952.html
Sent from the Solr - User mailing list archive at Nabble.com.
0 documents, you will create 8500 segments,
>> and that's not counting merges.
>>
>> How big are your documents? I just created an 850,000 document (and a
>> 3.5 m doc index) with tiny documents (id and title), and they deleted
>> quickly (17 milliseconds).
&g
000 document (and a
> 3.5 m doc index) with tiny documents (id and title), and they deleted
> quickly (17 milliseconds).
>
> Maybe if you post your delete code? Are you doing anything else (like
> commit/optimize?)
>
> Tom
>
>
>
> On Wed, Dec 8, 2010 at 12:55 PM, Ravi
s (id and title), and they deleted
quickly (17 milliseconds).
Maybe if you post your delete code? Are you doing anything else (like
commit/optimize?)
Tom
On Wed, Dec 8, 2010 at 12:55 PM, Ravi Kiran wrote:
> Hello,
>
> Iam using solr 1.4.1 when I delete by query or Id from solr
Hello,
Iam using solr 1.4.1 when I delete by query or Id from solrj it
is very very slow almost like a hang. The core form which Iam deleting has
close to 850K documents in the index. In the solrconfig.xml autocommit is
set as follows. Any idea how to speed up the deletion process
: Here's the problem: the standard Solr parser is a little weird about
: negative queries. The way to make this work is to say
: *:* AND -field:[* TO *]
the default parser actually works ok ... it's a bug specific to
deletion...
https://issues.apache.org/jira/browse/SOLR-381
-Hoss
that I didn't know?
> >>
> >> -date_added_solr:[* TO *]'
> >>
> >> - Original Message -
> >> From: "Max Lynch"
> >> To:
> >> Sent: Thursday, August 26, 2010 6:12 AM
> >> Subject: Delete by query issue
&g
;date_added_solr'? Is
>> this some kind of new query format that I didn't know?
>>
>> -date_added_solr:[* TO *]'
>>
>> - Original Message -
>> From: "Max Lynch"
>> To:
>> Sent: Thursday, August 26, 2010 6:12 AM
>> Subject: Delet
now?
>
> -date_added_solr:[* TO *]'
>
> - Original Message -
> From: "Max Lynch"
> To:
> Sent: Thursday, August 26, 2010 6:12 AM
> Subject: Delete by query issue
>
>
> > Hi,
> > I am trying to delete all documents that have null values for
Excuse me, what's the hyphen before the field name 'date_added_solr'? Is this
some kind of new query format that I didn't know?
-date_added_solr:[* TO *]'
- Original Message -
From: "Max Lynch"
To:
Sent: Thursday, August 26, 2010 6:12 AM
Subject: D
Hi,
I am trying to delete all documents that have null values for a certain
field. To that effect I can see all of the documents I want to delete by
doing this query:
-date_added_solr:[* TO *]
This returns about 32,000 documents.
However, when I try to put that into a curl call, no documents get
Cool, thanks - just wanted to make sure I'm not insane. Makes sense
that there would be a difference if the index is built fresh in that
case.
On Tue, Feb 16, 2010 at 11:59, Mark Miller wrote:
> Mat Brown wrote:
>> Hi all,
>>
>> Trying to debug a very sneaky bug in a small Solr extension that I
>
1 - 100 of 116 matches
Mail list logo
