Ah, that's what _root_ is for ! I was wondering.
Thank you!
On 7/25/18 2:36 PM, Mikhail Khludnev wrote:
_root_:parent-id
чт, 26 июля 2018, 1:33 TK Solr :
The child doc transformer worked great. Thank you.
In my experiment, posting 'parent-id' to the
update
end point only deleted the
I just now tried it with Solr7.4 and am getting the same symptoms as I describe
below.
The symptoms I describe are quite different from my impression of Shawn
Heisey's impression of my symptoms, so I will describe my symptoms again.
Let us assume that we start with a SolrCloud of two nodes:
_root_:parent-id
чт, 26 июля 2018, 1:33 TK Solr :
> The child doc transformer worked great. Thank you.
>
> In my experiment, posting 'parent-id' to the
> update
> end point only deleted the parent doc. Do I insert a complex join query
> from id
> to _version_ and delete all the docs of the
The child doc transformer worked great. Thank you.
In my experiment, posting 'parent-id' to the update
end point only deleted the parent doc. Do I insert a complex join query from id
to _version_ and delete all the docs of the matching _version_ ?
On 7/24/18 9:27 PM, TK Solr wrote:
Thank
On 7/25/2018 10:38 AM, Staley, Phil R - DCF wrote:
> What are the steps for upgrading a non-clustered SOLR version? Here's what I
> thought should work:
That depends on how you did the initial install.
If you used the service installer script that's included with Solr to do
the initial
Christopher,
I'll test it tomorrow and let you know! Thanks again!
Phil
-Original Message-
From: Christopher Schultz
Sent: Wednesday, July 25, 2018 3:40 PM
To: solr-user@lucene.apache.org
Subject: Re: Upgrading SOLR (not clustered)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Phil,
On 7/25/18 4:38 PM, Staley, Phil R - DCF wrote:
> Christopher,
>
> Testing an upgrade from version 7.2.1 to 7.4.0 on SUSE Linux 12
>
> From the /etc/init.d/solr file?
>
> SOLR_INSTALL_DIR="/opt/solr"
>
> From the /etc/default/solr.in.sh
Christopher,
Testing an upgrade from version 7.2.1 to 7.4.0 on SUSE Linux 12
From the /etc/init.d/solr file?
SOLR_INSTALL_DIR="/opt/solr"
From the /etc/default/solr.in.sh file? (and these are my data and/indexing core
locations
SOLR_PID_DIR="/var/solr"
SOLR_HOME="/var/solr/data"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Phil,
On 7/25/18 12:38 PM, Staley, Phil R - DCF wrote:
> What are the steps for upgrading a non-clustered SOLR version?
> Here's what I thought should work:
>
>
>
> 1. Open a bash window and ssh login to desired server with
> your Linux
https://lucene.apache.org/solr/guide/7_4/spatial-search.html#indexing-geojson-and-wkt
?
Regards,
Alex.
On 25 July 2018 at 16:15, SolrUser1543 wrote:
> I have look in reference guide and different wiki articles , but have not
> found anywhere an example of how index geojson .
>
> I have the
I have look in reference guide and different wiki articles , but have not
found anywhere an example of how index geojson .
I have the following field definition :
how should post request looks like in order to put geojson in this field ?
I have managed to index WKT , but not geojson .
--
Ah, so I could index the text including the § character as an alpha, use no
qs value when trying to ignore it, and for users add i a qs value assuming
I use edismax, whic I currently am.
Tested this method and it works as expected. Thanks, saved me a lot of
time!
-David
On Wed, Jul 25, 2018 at
If you copyField and don't store the copy, then it is only the indexed
(term) representation for the copy that is much smaller. Just a
thought.
The other thing is that you seem to be saying that you want to do a
match phrase but with a token gap, right? Like an eDisMax slop?
Hey all. have a situation that seems pretty rough. currently in our data
we have a lot of sentences like this:
elements comprise the "stuff" of the tax. 3 Reg. § 1.901-2(a)(2). 4 Only
non-Saudis are subject to the
FieldValueCache is used by faceting, mostly. So, you would need to execute
warm faceting queries to pre-populate it. More info in this old mailing
list topic:
http://lucene.472066.n3.nabble.com/Loading-data-to-FieldValueCache-tp4175721.html
Cheers,
Edward
Em qua, 11 de jul de 2018 02:09,
@shawn Heisey,
My client is facing the same issue. However, I am not sure / have not worked
with the ZkCli script in Zookeeper. Could you please help me with the steps?
If you could send me, where can I find the ZkCli script associated with
Zookeeper and the exact commands to run from each node,
What are the steps for upgrading a non-clustered SOLR version? Here's what I
thought should work:
1. Open a bash window and ssh login to desired server with your Linux
admin credentials
2. Change directories: cd /opt
3. Download the latest Linux/OSX version direct to
: Subject: MetricsHistoryHandler getOverseerLeader fails when hostname contains
: hyphen
that's unfortunate. I filed a jira...
https://issues.apache.org/jira/browse/SOLR-12594
: Can one just ignore this warning and what will happen then?
I think as long as you don't care about the
Hello!
We encounter a lot of log warning entries from the MetricsHistoryHandler saying
o.a.s.h.a.MetricsHistoryHandler Unknown format of leader id, skipping:
244550997187166214-server1-b.myhost:8983_solr-n_94
I don't even know what this _MetricsHistoryHandler_ does, but at least
Hi All,
From Solr Admin interface, I have created a collection and added field
definitions. I can get its managed-schema from the Admin interface.
Can I use this managed-schema to create a new collection? If yes, how?
Thanks,
Chuming
What are the steps for upgrading a non-clustered SOLR version? Here's what I
thought should work:
1. Open a bash window and ssh login to desired server with your Linux
admin credentials
2. Change directories: cd /opt
3. Download the latest Linux/OSX version direct to
When you specify sort order, Solr makes no assumptions at all. So
sort = asc would sort _only_ by key. Imagine how
puzzled people would be if they specify sort= asc and... the result
was really ordered by score. Yuck.
So yes, you must specify both.
Best,
Erick
On Tue, Jul 24, 2018 at 11:37 PM,
I have look in reference guide and different wiki articles , but have not
found anywhere an example of how index geojson .
I have the following field definition :
how should post request looks like in order to put geojson in this field ?
I have managed to index WKT , but not geojson .
--
: For deep pagination, it is recommended that we use cursorMark and
: provide a sort order for as a tiebreaker.
:
: I want my results in relevancy order and so have no sort specified on my
query by default.
:
: Do I need to explicitly set :
:
: sort : score desc, asc
Yes.
: Or can
> I think n-grams sounds like the only way to get this done.
You don't have to settle for "the only way". You can totally have the
same field(s) copyFielded into multiple locations and then have each
target field use a different indexing pipeline, including ngrams,
phonetic processing, full match
If you're not familiar with the edismax query parser, that's often what
people use to fire the query off against more than one field without
having the users be aware of it. That means you could ngram
the e-mail field and when a user types something in the search
box search against both the "all"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chris,
On 7/24/18 4:46 PM, Chris Hostetter wrote:
>
> : We are using Solr as a user index, and users have email
> addresses. : : Our old search behavior used a SQL substring match
> for any search : terms entered, and so users are used to being
q=*:*={!parent which="doc_type:parent"}+doc_type:child -child_color:*
Make sure that + isn;t grabbed by url encoding.
On Wed, Jul 25, 2018 at 8:23 AM sagandhi wrote:
> Hi Mikhail,
>
> Thank you for suggesting to use json facet. I tried json.facet, it works
> great and I am able to make a
Hi,
For deep pagination, it is recommended that we use cursorMark and provide a
sort order for as a tiebreaker.
I want my results in relevancy order and so have no sort specified on my query
by default.
Do I need to explicitly set :
sort : score desc, asc
Or can I get away with
29 matches
Mail list logo
