/*
 * Copyright (C) 2008 The Guava Authors
 *
 * Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except
 * in compliance with the License. You may obtain a copy of the License at
 *
 * http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software distributed under the License

import org.opensearch.index.query.BoolQueryBuilder;
import org.opensearch.index.query.CommonTermsQueryBuilder;
import org.opensearch.index.query.ExistsQueryBuilder;
import org.opensearch.index.query.IdsQueryBuilder;
import org.opensearch.index.query.MatchPhrasePrefixQueryBuilder;
import org.opensearch.index.query.MatchPhraseQueryBuilder;
import org.opensearch.index.query.MatchQueryBuilder;
import org.opensearch.index.query.PrefixQueryBuilder;

- The scheduler skips the `PodTopologySpread` Filter plugin if no spread constraints.
  It will affect some metrics values related to the `PodTopologySpread` Filter plugin. ([#117683](https://github.com/kubernetes/kubernetes/pull/117683), [@utam0k](https://github.com/utam0k))

behavior of some watch calls to the server when filtering on fields was incorrect.  If watching objects with a filter, when an update was made that no longer matched the filter a DELETE event was correctly sent.  However, the object that was returned by that delete was not the (correct) version before the update, but instead, the newer version.  That meant the new object was not matched by the filter.  This was a regression from behavior between cached watches on the server side and uncached watches, and...

{\n      this.minimize()\n      return\n    }\n\n    this.maximize()\n  }\n\n  // Private\n\n  _init(card) {\n    this._parent = card\n\n    $(this).find(this._settings.collapseTrigger).click(() => {\n      this.toggle()\n    })\n\n    $(this).find(this._settings.maximizeTrigger).click(() => {\n      this.toggleMaximize()\n    })\n\n    $(this).find(this._settings.removeTrigger).click(() => {\n      this.remove()\n    })\n  }\n\n  // Static\n\n  static _jQueryInterface(config) {\n    let data = ...

pkg image/png, type UnsupportedError string
pkg index/suffixarray, func New([]uint8) *Index
pkg index/suffixarray, method (*Index) Bytes() []uint8
pkg index/suffixarray, method (*Index) FindAllIndex(*regexp.Regexp, int) [][]int
pkg index/suffixarray, method (*Index) Lookup([]uint8, int) []int
pkg index/suffixarray, method (*Index) Read(io.Reader) error
pkg index/suffixarray, method (*Index) Write(io.Writer) error

- Fix a regression that the scheduler always goes through all Filter plugins. ([#114524](https://github.com/kubernetes/kubernetes/pull/114524), [@Huang-Wei](https://github.com/Huang-Wei)) [SIG Scheduling]

- A new metric `apiserver_request_filter_duration_seconds` has been introduced that 
  measures request filter latency in seconds. ([#95207](https://github.com/kubernetes/kubernetes/pull/95207), [@tkashem](https://github.com/tkashem)) [SIG API Machinery and Instrumentation]

  </mime-type>

  <mime-type type="application/im-iscomposing+xml"/>
  <mime-type type="application/index"/>
  <mime-type type="application/index.cmd"/>
  <mime-type type="application/index.obj"/>
  <mime-type type="application/index.response"/>
  <mime-type type="application/index.vnd"/>

  <mime-type type="application/inf">
    <_comment>Windows setup INFormation</_comment>

  * You can find out what taints you have in place on a node while you are still running Kubernetes 1.5 by doing `kubectl describe node <node name>`; the `Taints` section will show the taints you have in place. To see the taints that were created under 1.5 when you are running 1.6, do `kubectl get node <node name> -o yaml` and look for the "Annotation" section with the annotation...