-
### Elasticsearch Version
8.15.3
### Installed Plugins
_No response_
### Java Version
_bundled_
### OS Version
Cloud
### Problem Description
Running a `text_expansion` query against a field t…
-
### Is your feature request related to a problem? Please describe.
There is a variety of metadata we wish to capture and present in `uds-marketplace`. Presently, we are supplementing Zarf package m…
-
Currently during sampling, the expansions are stored as the source resource. E.g., Member. However, when these items are expanded, they are done as ListAgent, CoListAgent, etc. We should track the fie…
-
Currently the url for the source document is captured. The information obtained from the source for the case record can be buried within the document, perhaps requiring translation. In addition there …
-
#### Requested Feature
Currently in project.pros, there is a field called `upload_options` that allows users to specify default options for the upload command that will be applied by default, unless …
-
See this for details:
https://github.com/harfbuzz/boring-expansion-spec/issues/159
I suggest we implement that already. That is, if the `VariationStore` struct's `length` field is 65,535, then all…
-
Even if expressions are in inserts there is advantages to allowing numbered fields to avoid repeating the same expression. However, this can of course be worked around by storing the result in a tempo…
-
See this for details:
https://github.com/harfbuzz/boring-expansion-spec/issues/159
I suggest we implement that already. That is, if the `VariationStore` struct's length field is 65,535, then allow…
-
When a warning for "Fields of ‘SomeRecord’ not initialised: a, b, c, d" fires, I'd like a `CodeAction` that allows it to initialize all of those rows with typed holes.
Flow would look like this:
1…
-
There are times when a `ValueSet` contains an explicit expansion (for example when the terminology service does not contain the underlying code system)
We have a check [here] (https://github.com/me…