-
-
Notifications
You must be signed in to change notification settings - Fork 249
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[TASK] 11.6.x-dev Bump solr from 9.5.0 to 9.7.0 in /Docker/SolrServer #4146
Open
dependabot
wants to merge
20
commits into
release-11.6.x
Choose a base branch
from
dependabot/docker/Docker/SolrServer/release-11.6.x/solr-9.7.0
base: release-11.6.x
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
[TASK] 11.6.x-dev Bump solr from 9.5.0 to 9.7.0 in /Docker/SolrServer #4146
dependabot
wants to merge
20
commits into
release-11.6.x
from
dependabot/docker/Docker/SolrServer/release-11.6.x/solr-9.7.0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
As an initial steps to allow custom index queue types interfaces for queue and queue items are introduced. Additionally custom queue classes can be configured via: plugin.tx_solr.index.queue.<configurationName>.indexQueue This is a breaking change for all instances that implement own queues and queue items! Ports: #3764 Resolves: #3763
Queue initialization status returned by the QueueInitializationService isn't considered in the backend module and a success message is always shown. This commit adds a check for the returned status and displays an error message similiar to the message that is shown if an exceptions occured. Ports: #3764 Resolves: #3763
Existing exceptions are now based on the recently introduced generic EXT:solr exception. Additionally based on the new generic EXT:solr exception a further exception is introduced, allowing more targeted handling of exceptions: InvalidIndexQueueInitizalizationPostProcessorException This is a breaking change as the base excepion changed and the new exception is no longer based on \UnexpectedValueException. Ports: #3764 Resolves: #3763
Activates PHPStan in level 2 and performs required adaptions for this level.
This reverts commit 71e6ebc.
Updates to Apache Solr 9.2, this includes the required configuration updates. luceneMatchVersion is sill set to 8.5.0 to prevent changes in search behaviour. To avoid security issues described in CVE-2022-39135 the SQL module is not enabled, you have to enabled the module manually if required. Note: With Apache Solr 9 the following components are no longer available and you have to adapt the configuration if needed. No longer available components are: 1) Data Import Handler (DIH) DIH is an independent project now; it is no longer a part of Solr 2) VelocityResponseWriter VelocityResponseWriter is an independent project now; it is no longer a part of Solr. This encompasses all previously included /browse and wt=velocity examples. This update is considered as breaking, as a new Solr server and configset is required, but though not recommended you can still use your old configset and Solr 8.5 if an update is not possible. Ports: #3673
This adds a startup script which disables all unneeded cores. Usage: `docker run -e 'TYPO3_SOLR_ENABLED_CORES=english german' -it typo3solr/ext-solr` This enables only the english and german core (core_en, core_de) during startup. If the env variable is not set, then all cores are enabled (= default behaviour). The additional cores can be enabled afterwards by adding them to the TYPO3_SOLR_ENABLED_CORES env. variable. Ports: #3503
…uild This change makes it possible to change solr unix GID:UID on docker image build time. It is required for dev. environments and custom setups of EXT:solr docker containers. Ports: #3689
Note this change requires on third party installations enabling stream feature via the ENV vars or system properties. Following variables are set in Docker images: * `SOLR_ENABLE_REMOTE_STREAMING=true` * `SOLR_ENABLE_STREAM_BODY=true` For more information see: * https://solr.apache.org/guide/solr/latest/upgrade-notes/major-changes-in-solr-9.html#security * https://issues.apache.org/jira/browse/SOLR-14853 Ports: #3748
Since Apache Solr 9 the Unified Highlighter is used by default, causing the fragment size setting to be ignored in our setup. By configuring the Original Highlighter as default, this issue is fixed till we update our highlighting setup to use the recommended highlighter. Ports: #3802
Updates the supported and recommended Solr version to Apache Solr 9.5.0.
Relates: #3985
Bumps solr from 9.5.0 to 9.7.0. --- updated-dependencies: - dependency-name: solr dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
dependencies
Pull requests that update a dependency file
docker
Pull requests that update Docker code
labels
Sep 10, 2024
dkd-kaehm
added a commit
to dkd-kaehm/ext-solr
that referenced
this pull request
Sep 30, 2024
This change fixes the access restrictions stack within TYPO3 13. There were multiple troubles in classes and in integration tests. The page indexer stack on live system runs in multiple isolated processes: 1. CLI 2. first FE request to get FE-groups 3. multiple FE requests to get real content from page for desired FE-groups combination unlike on integration test running the page indexer steps allways on single process. This requires to unset the produced state on each step of indexing process. The runtime cache was interfering between the steps and did things that had nothing to do withhin the own step. --- The main problem within access restriction stack on page indexing was the registration of Event-Listeners methods within `UserGroupDetector` with `#[AsEventListener]` on EXT:solr. Due of current troubles with circular dependencies the auto-wiring and auto-configuration was disabled in Servvices.yaml globally. It requires to enable this features manually for classes, which was done for `UserGroupDetector` class. Relates: TYPO3-Solr#3995 Fixes: TYPO3-Solr#4146
dkd-friedrich
force-pushed
the
release-11.6.x
branch
from
October 30, 2024 13:45
8a08572
to
a88d39e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
dependencies
Pull requests that update a dependency file
docker
Pull requests that update Docker code
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bumps solr from 9.5.0 to 9.7.0.
You can trigger a rebase of this PR by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)