Hi Matthew
All the fields in your schema are required="true". This means they are
required for all documents, whether parents or children (or standalone).
"Required" fields (from a business logic perspective) on parents and
children will usually be different and that can't be enforced in a Solr
sc
Hi ,
Please subscribe me to the mailing list
Thanks,
Arun
On Thu, 27 Oct 2022 at 18:20, Arun sasikumar wrote:
> Hi ,
>
> Please subscribe me to the mailing list
>
To subscribe to the Solr User List, please send mail to
users-subscr...@solr.apache.org with "subscribe" in the subject line,
rather than sending mail directly to the user list. Please see
ht
Thank you, Thomas! Changing the required to false allowed the document to be
indexed. I did not gleam this information from the SOLR documentation regarding
nested documents. Do you know of any good sources for educational material on
this subject? I cannot change the payloads that I am working
Well honestly it’s more or less implied that if a field is declared required,
it’s required in all documents, parent or children. Perhaps an inherit field
would have been applicable if such exists(I don’t think so) and it’s documented
quite clearly here:
https://solr.apache.org/guide/solr/late
Thanks Fredrik for creating https://issues.apache.org/jira/browse/SOLR-16502
and providing an easy to reproduce test case. I just put a PR up to fix
this.
For those looking for a great bug report this is an awesome example.
Kevin Risden
On Wed, Oct 26, 2022 at 6:14 AM solr wrote:
> Hi
>
> We’
Bumping this to the list again in case anyone has any insights before I
open an issue in JIRA for this.
Op do 20 okt. 2022 om 00:41 schreef Thomas Corthals :
> Hi,
>
>
> I'm running into an exception with Solr 9.0.0 for a request that works
> fine with Solr 8.11.2 and I have no idea why.
>
>
> I'
Thank you for your response. I don't like the denormalization approach for
3 reasons-
- More memory
- Increased efforts to keep the document in sync
- Filter out copies of documents from search if different copies of the
same document are returned in the search result because their locations are
qu
On 10/26/22 02:17, Alex The Rocker wrote:
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.
Good question, which Jan seems t
On 10/19/22 16:41, Thomas Corthals wrote:
I'm running into an exception with Solr 9.0.0 for a request that works fine
with Solr 8.11.2 and I have no idea why.
However, if I don't do a commit between the two adds, I don't get the error.
Did something change between Solr 8 and 9 that I have to
Op do 27 okt. 2022 om 22:04 schreef Shawn Heisey :
> On 10/19/22 16:41, Thomas Corthals wrote:
> > I'm running into an exception with Solr 9.0.0 for a request that works
> fine
> > with Solr 8.11.2 and I have no idea why.
>
> > However, if I don't do a commit between the two adds, I don't get the
On 10/27/22 15:51, Thomas Corthals wrote:
I can reproduce it on a pristine techproducts example index by unpacking
the Solr 9.0.0 download and changing the schema in the sample configset
*before* I even start that Solr instance for the very first time. That
should rule out a conflict between the
Hi all,
has anyone gone through the exercise of replacing Data Import Handler
with scripts that POST JSON and if so, are your scripts still working OK
with 8.11.2?
I got a few that work fine with 6.5 and 8.7 but are throwing 503s and
occasional 400s all over the place with 8.11.2.
Solr isn
You are using three features together
A) Nested docs
B) Price field (which is really storing price and currency in two sub fields)
C) Atomic updates
I would not be surprised if these three are not really compatible.
Since there is a requiement to ALWAYS index the entire block of parent and
childr
> On Oct 27, 2022, at 5:44 PM, dmitri maziuk wrote:
>
> has anyone gone through the exercise of replacing Data Import Handler with
> scripts that POST JSON and if so, are your scripts still working OK with
> 8.11.2?
That's exactly what I've done a couple of years ago and they work just fine
15 matches
Mail list logo
