Thank you so much for your response, Thomas, I do appreciate it.
I made the changes, but I am getting a different error now. Did I not interpret
your instructions correctly?
https://i.postimg.cc/SNM4t7vs/updated-schema.png
https://i.postimg.cc/RZtcF8bB/Screenshot-2022-10-26-170222.png
__
Hi all,
Jason Gerlowski and I are excited to do the second Contributor Workshop with
interested folks on November 3rd. We will dig into an area of Solr ideal for
new contributors: the "v2 APIs” in this workshop.
We retro’ed the first one and made a couple of changes:
1) Calling them Workshop
I’d love to see some new content, and yeah, I think that section on Spatial
Queries is a remnant of a previous clean up of the page! Feel free to tag me
with any PR’s on the docs!
> On Oct 26, 2022, at 1:14 PM, Samuel Smith wrote:
>
> Hey Listers … Does this page look right?
>
> https://sol
Hey Listers … Does this page look right?
https://solr.apache.org/guide/solr/latest/getting-started/solr-tutorial.html
Seems to me it skips a lot of the start-up / set-up commands and dives
(prematurely?) into a section about Spatial Queries. It’s not consistent
with the equivalent Solr 8.x page.
Hi Solr Community,
I have been looking into the v2 API and testing it with solr 9. On a local
installation (single node, cloud mode), I can access the API and it all
works as I would expect. However when I tested the same on a cloud
installation (multi node, multi shard, dedicated overseer, extern
Hello Jan,
It was a user error! I had conflicting Lucene versions..:-(
Thanks
Ed
On Tuesday, October 25, 2022 at 12:48:43 AM PDT, Jan Høydahl
wrote:
Hi,
Can you be more specific on what libraries you try to use, and how you added
them in Solr 8?
The reference guide may help you:
h
I believe it is a hotspot JIT compiler specific bug.
Jan Høydahl
> 26. okt. 2022 kl. 10:18 skrev Alex The Rocker :
>
> Hello,
>
> Is this bug with Solr with Java 17 specific to HotSpot-based JVMs ?
>
> FYI I'm running Solr 8.11.2 in production for a while with IBM Semeru
> 17 (based on OpenJ9
Hi
We’ve stumbled upon something that seems like a bug. The behaviour is changed
since solr 8.11
If we setup copyfield with maxChars, this is “remembered” for all other
copyField-operations (at least for the same source field).
From schema.xml:
Input doc:
body:“On a brighter note, they ha
Hello,
Is this bug with Solr with Java 17 specific to HotSpot-based JVMs ?
FYI I'm running Solr 8.11.2 in production for a while with IBM Semeru
17 (based on OpenJ9 JVM) on CentOS 7.9 x64, and I have not observed
such crashes.
Alex
Le mar. 25 oct. 2022 à 10:32, Jan Høydahl a écrit :
>
> Severa
