Can we commit the security policy addition independently?
On Thu, Jun 3, 2021 at 2:20 PM Michael Gibney
wrote:
> Ok, I think I've got this now. jars from the mavenLocal() repo are used
> in-place by gradle, and not cached in `${gradle.lib.dir}`. This requires a
> security policy addition to
>
Ok, I think I've got this now. jars from the mavenLocal() repo are used
in-place by gradle, and not cached in `${gradle.lib.dir}`. This requires a
security policy addition to
`gradle/testing/randomization/policies/solr-tests.policy`:
grant {
// Allow reading gradle worker JAR.
permission
Hi,
A colleague of mine investigated that in conjunction with DocValues some
time ago:
*Intro*
enableLazyFieldLoading is a query time configuration that regulates how
field values are retrieved from the index data structures and returned to
the user via search results.
Currently Apache Solr
These may be interesting and relevant:
*
https://solr.apache.org/guide/8_8/query-settings-in-solrconfig.html#enablelazyfieldloading
*
https://solr.apache.org/guide/8_8/defining-fields.html#optional-field-type-override-properties
(last entry "large")
Regards,
Alex.
On Thu, 3 Jun 2021 at
Hello experts!
In ES, even a client specified only id fields to retrieve, it tries to
lookup stored fields after acquired document ids for it's own good.
https://github.com/elastic/elasticsearch/blob/master/server/src/main/java/org/elasticsearch/search/fetch/FetchPhase.java#L109
I just wonder
