Thanks
On Fri, Apr 19, 2019 at 7:58 PM Erick Erickson
wrote:
> Yep. There’s no euqivalent of an RDBMSs composite key in Solr OOB.
>
> > On Apr 19, 2019, at 4:28 PM, Vivekanand wrote:
> >
> > When you say roll your own , you mean , create a single field by
> > concatenation so that the result is
Yep. There’s no euqivalent of an RDBMSs composite key in Solr OOB.
> On Apr 19, 2019, at 4:28 PM, Vivekanand wrote:
>
> When you say roll your own , you mean , create a single field by
> concatenation so that the result is unique ? Like USER_RECORD_12334 ?
>
> On Friday, April 19, 2019, Erick E
When you say roll your own , you mean , create a single field by
concatenation so that the result is unique ? Like USER_RECORD_12334 ?
On Friday, April 19, 2019, Erick Erickson wrote:
> Basically you have to roll your own. You could do this when you assemble
> the document on the client or use a
Basically you have to roll your own. You could do this when you assemble the
document on the client or use an UpdateRequestProcessor. If the latter, by
very, very sure you get it in the right place, specifically _before_ the doc is
routed.
But I’d just assemble it on the client when I created t
Hi
According to the documentation, facet.sort options could be count(sort by
highest count), index (sort lexicographically).
If I have set facet.sort to count, and the resulting facet fields have the same
count then how is the list returned?
Is there any other option that controls in this case?
Hello,
I have a use case like below.
*USE CASE*
I have a document with fields like
Id,
Id_type,
Field_1.
Filed_2
2 sample messages will look like
{
"id": "12334",
"id_type": "USER_RECORD",
"field_1": null,
"field_2": null
}
{
"id": "31321",
"id_type": "OWN
Hello,
I have a use case like below.
USE CASE
I have a document with fields like
Id,
Id_type,
Field_1.
Filed_2
2 sample messages will look like
{
"id": "12334",
"id_type": "USER_RECORD",
"field_1": null,
"field_2": null
}
{
"id": "31321",
"id_type": "OWNER_RECORD",
"field_1": n
Hi
According to the documentation, facet.sort options could be count(sort by
highest count), index (sort lexicographically).
If I have set facet.sort to count, and the resulting facet fields have the same
count then how is the list returned?
Is there any other option that controls in this case?
Ok I updated the ticket, we can move the discussion there.
Joel Bernstein
http://joelsolr.blogspot.com/
On Fri, Apr 19, 2019 at 7:44 AM David Barnett wrote:
> Hi Joel
>
> BUG created in jira SOLR-13414
>
> Please let me know if you need more info
>
> Thanks
>
> Dave
> On 18 Apr 2019, 20:50 -05
Hi Joel
BUG created in jira SOLR-13414
Please let me know if you need more info
Thanks
Dave
On 18 Apr 2019, 20:50 -0500, Joel Bernstein , wrote:
> That stack trace points here:
> https://github.com/apache/lucene-solr/blob/releases/lucene-solr/7.3.0/solr/core/src/java/org/apache/solr/handler/sql
Hi Kevin
We have the same outcome on systems with a single shard (the original host) and
also a system where we have created a replica on the same host
The import / export does not to my knowledge create a new shard but I can
confirm
On 18 Apr 2019, 20:53 -0500, Kevin Risden , wrote:
> Do you h
11 matches
Mail list logo
