Add documentation re alphabetical sorted of MV dimensions

[lkm]

Simple updating of documentation. It's very relevant to know that that multi-value dimensions are sorted by default and that it's possible to change this behaviour.

To someone more intune with Druid's inner workings: Do we really want alphabetical sorted to be the default for MV dimensions? Would it not be better to default to ARRAY in DimensionSchema L89?

Description

Fixed the bug ...

Renamed the class ...

Added a forbidden-apis entry ...

---

This PR has:

• been self-reviewed.
  • using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)
• added documentation for new or modified features or behaviors.
• added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
• added or updated version, license, or notice information in licenses.yaml
• added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
• added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
• added integration tests.
• been tested in a test Druid cluster.

---

Key changed/added classes in this PR

• MyFoo
• OurBar
• TheirBaz

[techdocsmith]

See comments. Please fix link style.

[techdocsmith]

Suggested change

	| multiValueHandling | Specify the type of handling multi-value fields will get, possible values are `SORTED_ARRAY`, `SORTED_SET` and `ARRAY`. The first two will order the array upon ingestion and `SORTED_SET` will remove duplicates. `ARRAY` will ingest data as-is | `SORTED_ARRAY` |
	| multiValueHandling | Specify the type of handling for multi-value fields. Possible values are `SORTED_ARRAY`, `SORTED_SET`, and `ARRAY`. `SORTED_ARRAY` and `SORTED_SET` order the array upon ingestion. `SORTED_SET` removes duplicates. `ARRAY` ingests data as-is | `SORTED_ARRAY` |

[techdocsmith]

Suggested change

	characters), by default they are sorted alphabetically, see [Dimension Objects](../ingestion/index.html#dimension-objects) for configuration.
	characters), by default Druid lists the values in alphabetical order, see [Dimension Objects](../ingestion/index.md#dimension-objects) for configuration.

Please use .md for links. Also, it's not clear to me what the related information is at the destination. But I'm a still fairly new to Druid.

[lkm]

Thanks @techdocsmith, I've updated the commit with your recommendations. "Lists" is the wrong verb here, "ingests" would be more appropriate. The referred section is the above committed detail about multiValueHandling.

[lkm]

Also .md should be .html, check the rest of the reference in the file. The markdown is compiled for the web version of the doc.

[techdocsmith]

@lkm , please see: #10528 Using .md is more flexible for viewing docs locally and for publishing to the web

[lkm]

Thanks for the context @techdocsmith, I've changed it to .md

[gianm]

I double-checked to make sure there are tests for this feature, and it looks like there are, so I think it's good to add the docs. (We wouldn't want to add docs for an untested feature!)

A couple of comments and then I think this is good to go.

[gianm]

To someone more intune with Druid's inner workings: Do we really want alphabetical sorted to be the default for MV dimensions? Would it not be better to default to ARRAY in DimensionSchema L89?

Probably ARRAY or maybe SORTED_SET would be an ideal default. SORTED_ARRAY is a little weird, admittedly, but it's the default for legacy reasons. Maybe we'll change it in a future version.

[lkm]

Thanks @gianm. Requested changes added

[sthetland]

LGTM