public class DocBoostMatcher {

    private String boostExpression = "0";

    private String matchExpression;

    private final String scriptType;

    public DocBoostMatcher() {
        scriptType = Constants.DEFAULT_SCRIPT;
    }

    public DocBoostMatcher(final BoostDocumentRule rule) {
        matchExpression = rule.getUrlExpr();
        boostExpression = rule.getBoostExpr();

* fix WaitForAttach failure issue for azure disk ([#62612](https://github.com/kubernetes/kubernetes/pull/62612), [@andyzhangx](https://github.com/andyzhangx))
* Pod affinity `nodeSelectorTerm.matchExpressions` may now be empty, and works as previously documented: nil or empty `matchExpressions` matches no objects in scheduler. ([#62448](https://github.com/kubernetes/kubernetes/pull/62448), [@k82cn](https://github.com/k82cn))

		<property name="threadDump">false</property>
		<postConstruct name="addBoostDocumentRule">
			<arg>
				<component class="org.codelibs.fess.indexer.BoostDocumentRule">
					<property name="matchExpression">"url.matches(\".*fess.*\")"</property>
					<property name="boostExpression">"1000.0"</property>
				</component>
			</arg>
		</postConstruct>
		 -->
	</component>
	<component name="crawlerStatsHelper"

- Fixes a regression in v1beta1 PodDisruptionBudget handling of `strategic merge patch`-type API requests for the `selector` field. Prior to 1.21, these requests would merge `matchLabels` content and replace `matchExpressions` content. In 1.21, patch requests touching the `selector` field started replacing the entire selector. This is consistent with server-side apply and the v1 PodDisruptionBudget behavior, but should not have been changed for v1beta1. ([#108138...

### API Change

### API Change

### API Change