Re: Quick question about elevated results
Hi Solr users, Further to the below, elevation with match="subset" does not appear to work in the techproducts example for: * Solr 9.3.0 * Solr 8.11.2 * Solr 8.3.0 (when match="subset" was introduced) If anybody can shed any light on why this might be (or has seen this feature working!) please let me know. Otherwise I will file a bug report. Thanks in advance for your help Thomas From: Tom Chopin Sent: 25 July 2023 12:42 To: users@solr.apache.org Subject: Quick question about elevated results Hello Solr users, Please help with the following query about elevation in Solr 9.3.0. Elevation doesn't seem to get much attention in the mailing list archives, or Stack Overflow, so I'm wondering if I've found a bug. My docs are related to dentistry and my elevate.xml looks like this: When my query is only for the word "drill", the doc with ID 38 is elevated as expected. So elevation is definitely working. When my query is for the phrase "drill teeth", I would expect this to be elevated too, because match is set to "subset". However the elevation is ignored and nothing is elevated. Why is the subset parameter not behaving like the docs suggest? Thanks in advance! Best regards Thomas
solr 9.3.0 file permissions issues snapshot_metadata dir
Hi,
Trying to upgrade from 9.1.1 to the latest version solr 9.3.0,
encountered a file permissions issue specific to this directory
"snapshot_metadata" which is not seen in 9.1.1. It is there in 9.2.x and
the latest version.
org.apache.solr.common.SolrException:org.apache.solr.common.SolrException:
access denied ("java.io.FilePermission"
"/mnt/data/solr/solr/legacy_v1_s1_shard3_replica_n1/data/snapshot_metadata"
"read")
What is causing it? If this directory is only accessed by backup and
restore features, and if we don't use that feature, can we delete this
directory and work without it?
Thanks,
Rajani
Re: solr 9.3.0 file permissions issues snapshot_metadata dir
You'll probably want to look into your Java Security Policy settings
as that is what causes this error. You can see default security policy
included in the Solr distribution here:
https://github.com/apache/solr/blob/b9100ba775defbed5114dd92526382047ce611dc/solr/server/etc/security.policy#L4.
You'll want to make sure the right properties are being set for your
Solr data directory to ensure Solr has file permissions to that
directory.
On Wed, Jul 26, 2023 at 10:48 AM rajani m wrote:
>
> Hi,
>
>Trying to upgrade from 9.1.1 to the latest version solr 9.3.0,
> encountered a file permissions issue specific to this directory
> "snapshot_metadata" which is not seen in 9.1.1. It is there in 9.2.x and
> the latest version.
>
> org.apache.solr.common.SolrException:org.apache.solr.common.SolrException:
> access denied ("java.io.FilePermission"
> "/mnt/data/solr/solr/legacy_v1_s1_shard3_replica_n1/data/snapshot_metadata"
> "read")
>
> What is causing it? If this directory is only accessed by backup and
> restore features, and if we don't use that feature, can we delete this
> directory and work without it?
>
> Thanks,
> Rajani
PlacementPlugin to restrict two different shards of the same collection on the same node
Hello, We just migrated to Solr 9.2 and started using AffinityPlacementPlugin. In a sharded environment, we made sure there is enough storage on each node and enough nodes in each AZ, but it is interesting that shard1 and shard2 of the same collection were distributed on the same node. In Solr 8, it is by default not allowing 2 shards of the same collection on the same node. We looked into the PlacementPlugins code, and didn't see any restrictions against that. Does anyone have the same issue? Do you have any suggestions? Thank you very much, Jing
