[
https://issues.apache.org/jira/browse/SOLR-15038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17295203#comment-17295203
]
Bruno Roustant edited comment on SOLR-15038 at 3/4/21, 10:37 AM:
-----------------------------------------------------------------
Ouch, yes I'll revert that. I played with this permission but didn't intend to
commit it.
When running the tests I noticed many Solr tests have warning about being
unable to create some test resources.
{code:java}
java.security.AccessControlException: access denied ("java.io.FilePermission"
"lucene-solr/solr/core/build/resources/test/solr/userfiles" "write")
at
java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
~[?:?]
at java.security.AccessController.checkPermission(AccessController.java:897)
~[?:?]
at java.lang.SecurityManager.checkPermission(SecurityManager.java:322) ~[?:?]
at java.lang.SecurityManager.checkWrite(SecurityManager.java:752) ~[?:?]
at sun.nio.fs.UnixPath.checkWrite(UnixPath.java:824) ~[?:?]
at
sun.nio.fs.UnixFileSystemProvider.createDirectory(UnixFileSystemProvider.java:377)
~[?:?]
at java.nio.file.Files.createDirectory(Files.java:689) ~[?:?]
at java.nio.file.Files.createAndCheckIsDirectory(Files.java:796) ~[?:?]
at java.nio.file.Files.createDirectories(Files.java:742) ~[?:?]
at org.apache.solr.core.CoreContainer.<init>(CoreContainer.java:383) [main/:?]
at org.apache.solr.core.CoreContainer.<init>(CoreContainer.java:344)
[main/:?]{code}
I noticed they disappeared when I changed the permission for write-access in
solr-tests.policy.
[~dweiss] do you know how to get rid of these (many) warnings?
was (Author: broustant):
Ouch, yes I'll revert that. I played with this permission but didn't intend to
commit it.
When running the tests I noticed many Solr tests have warning about being
unable to create some test resources.
{code:java}
java.security.AccessControlException: access denied ("java.io.FilePermission"
"lucene-solr/solr/core/build/resources/test/solr/userfiles" "write")
at
java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
~[?:?]
at java.security.AccessController.checkPermission(AccessController.java:897)
~[?:?]
at java.lang.SecurityManager.checkPermission(SecurityManager.java:322) ~[?:?]
at java.lang.SecurityManager.checkWrite(SecurityManager.java:752) ~[?:?]
at sun.nio.fs.UnixPath.checkWrite(UnixPath.java:824) ~[?:?]
at
sun.nio.fs.UnixFileSystemProvider.createDirectory(UnixFileSystemProvider.java:377)
~[?:?]
at java.nio.file.Files.createDirectory(Files.java:689) ~[?:?]
at java.nio.file.Files.createAndCheckIsDirectory(Files.java:796) ~[?:?]
at java.nio.file.Files.createDirectories(Files.java:742) ~[?:?]
at org.apache.solr.core.CoreContainer.<init>(CoreContainer.java:383) [main/:?]
at org.apache.solr.core.CoreContainer.<init>(CoreContainer.java:344)
[main/:?]{code}
I noticed they disappeared when I changed the permission for write-access in
solr-tests.policy.
Do you know how to get rid of these (many) warnings?
> Add elevateDocsWithoutMatchingQ and onlyElevatedRepresentative parameters to
> elevation functionality
> ----------------------------------------------------------------------------------------------------
>
> Key: SOLR-15038
> URL: https://issues.apache.org/jira/browse/SOLR-15038
> Project: Solr
> Issue Type: Improvement
> Components: query
> Reporter: Tobias Kässmann
> Priority: Minor
> Fix For: 8.9
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> We've worked a lot with Query Elevation component in the last time and we
> were missing two features:
> * Elevate only documents that are part of the search result
> * In combination with collapsing: Only show the representative if the
> elevated documents does have the same collapse field value.
> Because of this, we've added these two feature toggles
> _elevateDocsWithoutMatchingQ_ and _onlyElevatedRepresentative._
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]