public static final String STOP = "stop";

    public static final String AUTO = "auto";

    public static final String NONE = "none";

    public static final String ITEM_LABEL = "label";

    public static final String ITEM_VALUE = "value";

    public static final String ITEM_NAME = "name";

    public static final String MS932 = "MS932";

        "The parameter is incorrect.", "Too many Uids active on this session.", "The Uid is not known as a valid user identifier on this session.",
        "The pipe has been ended.", "The filename, directory name, or volume label syntax is incorrect.", "The directory is not empty.",
        "Cannot create a file when that file already exists.", "All pipe instances are busy.", "The pipe is being closed.",

        "Too many Uids active on this session.",
        "The Uid is not known as a valid user identifier on this session.",
        "The pipe has been ended.",
        "The filename, directory name, or volume label syntax is incorrect.",
        "The directory is not empty.",
        "Cannot create a file when that file already exists.",
        "All pipe instances are busy.",
        "The pipe is being closed.",

        defaultDataMap.put(fessConfig.getIndexFieldCreated(), systemHelper.getCurrentTime());
        // boost
        defaultDataMap.put(fessConfig.getIndexFieldBoost(), config.getBoost().toString());
        // label: labelType
        // role: roleType
        final List<String> roleTypeList = new ArrayList<>();
        stream(config.getPermissions()).of(stream -> stream.forEach(p -> roleTypeList.add(p)));

  // When a driver is initialized on a node, it provides the same topology keys
  // along with values. Kubelet will expose these topology keys as labels
  // on its own node object.
  // When Kubernetes does topology aware provisioning, it can use this list to
  // determine which labels it should retrieve from the node object and pass
  // back to the driver.
  // It is possible for different nodes to use different topology keys.

fun String.canParseAsIpAddress(): Boolean = VERIFY_AS_IP_ADDRESS.matches(this)

/**
 * Returns true if the length is not valid for DNS (empty or greater than 253 characters), or if any
 * label is longer than 63 characters. Trailing dots are okay.
 */
internal fun String.containsInvalidLabelLengths(): Boolean {
  if (length !in 1..253) return true

  var labelStart = 0
  while (true) {

        },
        "datasource": {
          "type": "prometheus",
          "uid": "${datasource}"
        },
        "definition": "",
        "hide": 0,
        "includeAll": false,
        "label": "Namespace",
        "multi": false,
        "name": "namespace",
        "options": [],

      },
      "mimetype": {
        "type": "keyword"
      },
      "parent_id": {
        "type": "keyword"
      },
      "role": {
        "type": "keyword"
      },
      "label": {
        "type": "keyword"
      },
      "virtual_host": {
        "type": "keyword"
      },
      "segment": {
        "type": "keyword"
      },
      "site": {
        "type": "keyword"

        } catch( UnsupportedEncodingException uee ) {
        }
        dstIndex += scope.length();

        dst[dstIndex++] = (byte)0x00;

        // now go over scope backwards converting '.' to label length

        int i = dstIndex - 2;
        int e = i - scope.length();
        int c = 0;

        do {
            if( dst[i] == '.' ) {
                dst[i] = (byte)c;
                c = 0;

  // When a driver is initialized on a node, it provides the same topology keys
  // along with values. Kubelet will expose these topology keys as labels
  // on its own node object.
  // When Kubernetes does topology aware provisioning, it can use this list to
  // determine which labels it should retrieve from the node object and pass
  // back to the driver.
  // It is possible for different nodes to use different topology keys.