Hi
I am trying Solr 7.6 in SolrCloud mode.
But I found that ZooKeeper 3.4.11 has a critical issue about handling
data/log directories.
(https://issues.apache.org/jira/browse/ZOOKEEPER-2960)
So, I want to know if using ZooKeeper 3.4.12 with Solr 7.6 is safe.
Does anyone know this?
Thanks,
Hi,
I have questions about the IndexUpgrader tool.
- I want to upgrade from Solr 4 to Solr 7. Can I run upgrade the index from
4 to 5 then 5 to 6 and finally 6 to 7 using appropriate version of the
IndexUpgrader but without loading the Index in the Solr at all during the
successive upgrades.
-
I ingested some nested documents into a Solr 7.4 core . When I search with
the following it's not returning a child document that I expected:
```
{!child of=cont_type:overview}id:2
```
I can see that the document I'm looking for exists with the query:
```
q=id:2-1
```
I'm wondering
You can take a look a Solr Streaming expressions to see if it meets your
needs. The "jdbc" Stream and "search" streams can be combined using the
"merge" stream.
http://lucene.apache.org/solr/guide/7_6/stream-source-reference.html
Dear Team,
Once per day, my data importing tool will collect data from SQL server and
add it into SOLRCloud.
Current day data will be imported at the end of the day.
I want to apply search and sorting for all my data. For this case, how can I
combine & sort, both SQL and SOLR data?
Is it
Hi,
looking at the graph traversal capabilities of solr. Is there a
function/feature that traverses until certain pre-requisites are met?
For instance, in an hierarchical use case, "traverse all children until a child
has a certain name or type"?
Using the current nodes streaming
Hello, Koji.
Why don't request separate {!edixmax qf=filed mm=3}bar per field?
On Sat, Dec 15, 2018 at 9:23 AM Koji Sekiguchi
wrote:
> Hi,
>
> I have a use case that one of our customers wants to set different mm
> parameter per field,
> as in some fields of qf, unexpectedly many terms are
I'm still pretty clueless trying to find the root cause of this behavior. One
thing is pretty consistent that whenever a node restarts up and sends a
recovery command, the recipient shard/replica goes down due to sudden surge
in old gen heap space. Within minutes, it hits the ceiling and stall the
On Sun, Dec 16, 2018 at 05:44:30PM -0800, Erick Erickson wrote:
> No, the idea is that you have N single valued fields, one for each of
> the MV entries you have. The copyField dest would be MV, and only used
> in those cases you wanted to match across values. Not saying that's a
> great solution,
