Hi Thomas,
As I understood it there is the ConcurrentUpdateSolrClient for this. Am I
better off doing this myself or should I just use the concurrent client?
Is it correct that I could reach your described scenario by setting
withQueueSize to 200 (default is 10) and setting "solr.cloud.client.st
Dear Solr People
On our system we have an indexer-service that indexes documents based on
incoming events. Sometimes a lot of these events happen at the same time (or at
least very close in time to each other). If that happens our indexer receives
GOAWAY signals from solr.
We're using the HttpJ
Hello dear Solr Team
In my documents I use fields with field type text_de. Lately I came across
weird behavior with this field type. To reproduce these weird behavior I have
set up a local solr verver on my machine. There I could identify the same
behavior.
To reproduce it yourself, just set u
Hey All
Is there a migration Guide for Users coming from using
`ConcurrentUpdateSolrClient` who want to upgrade to
`ConcurrentUpdateHttp2SolrClient`?
It seems to not be as straightforward as upgrading from `HttpSolrClient` to
`Http2SolrClient`.
ConcurrentUpdateSolrClient has a Builder with th
Hi Jan Høydahl
Indeed, you are correct. That is very relieving.
So, what would be advice on version 9.0 - 9.5? Not using it in production, but
using 9.6+?
With kind regards,
Dario Viva
Hello Solr Team
I am a little bewildered about the counting capabilities of solr.
When I want to know how elements one would find for a given query, I set the
limit to 0.
But setting the limit to 0 somehow leads to a wrong count. Sometimes I get a
higher count that I would expect.
For example:
Dear Solr Team,
I am a little Confused as to what Client I should be using.
On the solr server we use version 9.5.0 and on the client side we use 9.4.1.
So, we are fully on the solr 9 train. (Can there be problems when client and
server are not using exactly the same version?)
Now the problem
Hey Jeremy
upsy-daisy, you are obviously correct. I thought that I have tried the sort,
but obviously I have not. Because today the sorting worked as expected and was
case-insensitive.
The stored value still maintains the original value, but that kind of makes
sense, as otherwise what would be
Dear Solr Team
I have documents where I want to index a field twice. One time as a normal
string, and another time as a lowercase string.
I have not changed the default managed-shema.xml.
There the two corresponding dynamic fields are configured.
[...]
[...]
[...]
But still, the content of
Hi Hoss
I feel so stupid right now, thank you so much!
Of course this makes much more sense. Why should we want to have different
Timezones for different facets. Hopefully I don't come across as being
sarcastic, I really think that it makes more sense that it's a global modifier.
After reading t
Small correction:
> This will now be 1 day off for all future winter months that are preceded by
> a 30 day month, and 2 days and 1 hours off for all summer months preceded by
> a 31 day month.
Not that it matters all too much.
Von: Viva Dario
Gesendet: Donnerstag, 16. Mai 12024 19:30
An: users
Dear Solr Team,
One use case we have with solr (we use 9.5) is to facet over months on a
specific fields in our documents. We want to know how many documents there are
each Month.
But as you probably have guessed, the users of our app don't life in Greenwich
(also their time changes two times a
bug": {
> "time": 0
> }
> }
> },
> "rawquerystring": "task_coopProcessId:20021454",
> "que
Hello Mikhail,
The Fieldtype is plong. Hopefully this helps us find the problem.
As I can not send you screenshots I will attempt to send you an ascii
representation of what I see under the Schema endpoint in the web admin view.
Field
task_coopProcessId
Type
Plong
Field: task_coopProcessId
Fie
"value": 0,
"description": "task_coopProcessId:[20021454 TO
20021454] doesn't match id 30378"
},
"task_46915": {
"match
Hello All,
We have a relatively new Solr Instance:
solr-spec: 9.5.0
solr-impl: 9.5.0 cdd27dd15c3a6574032e9b1b92b148ab4e383599 - gerlowskija -
2024-02-07 15:10:39
lucene-spec: 9.9.2
lucene-impl: 9.9.2 a2939784c4ca60bc28bf488b5479c02fc2e5e22c - 2024-01-25
09:51:09
JVM Runtime: Eclipse Adoptium O
Hello All,
We have a relatively new Solr Instance:
solr-spec: 9.5.0
solr-impl: 9.5.0 cdd27dd15c3a6574032e9b1b92b148ab4e383599 - gerlowskija -
2024-02-07 15:10:39
lucene-spec: 9.9.2
lucene-impl: 9.9.2 a2939784c4ca60bc28bf488b5479c02fc2e5e22c - 2024-01-25
09:51:09
JVM Runtime: Eclipse Adoptium O
... But this is not really an elegant solution. As we would need to do a find
and replace on the whole search string, and depending on what tokenizer was
used, we would need to replace different characters.
On 2024/01/24 08:10:41 da...@coop.ch wrote:
> Hello all
>
> We have fields on documents t
Hello all
We have fields on documents that contain special characters. (e.g. "-", "@" or
"/" ...)
Now when we want to search on this field we encountered some weird behavior.
Hopefully you guys can help.
Let's suppose we have the fallowing Document:
{
"id":"id_number",
"content":"He
Hey Shawn
I know that this specific API exists in java. I also used it before and it
works as it should.
But my Question was specificly about arbitrary ranges, this API only accepts
start, end and gap. Which is fine for a lot of use cases, but sometimes one
wants to have custom sized ranges and
Hello Everyone at Solr
When someone wants build a range facet with arbitrary range one could build a
request with the help of the fallowing documentation.
https://solr.apache.org/guide/8_6/json-facet-api.html#arbitrary-range
But when you want to use this from java with the solrj client I did not
Hello Everyone at Solr
This Email is possibly a duplicate, but as I did not find my Mail appear in the
archives the first time I'm sending it a second time.
Today I wanted to bump the Spring Boot version from 3.1.7 to 3.2.1.
With the first Version my application just worked, but now I get the
22 matches
Mail list logo
