Austin Godber

We're going to punt on this until there's a more direct need which might help clarify the implementation details. A few things we realized is: * What would the signal...

This hasn't turned out to be much of a real problem, closing until it does.

Looking at what the commands would look like, if we unified them: ``` teraslice Commands: teraslice aliases commands to add and remove cluster aliases teraslice assets commands to manage assets...

I'll say no and err on the side of closing. We can always re-open.

One noteworthy thing here. Both Jared and Peter tried to reproduce this issue but couldn't. Speaking with Jared, his mapping had `keyword` for the `NAME` field, while as mine is...

Strangely a similar query for `STATION` works: ``` "STATION": { "type": "text", "fields": { "keyword": { "type": "keyword", "ignore_above": 256 } } }, ``` These three queries return what I'd...

Note, the examples in this issue are all from a sample NOAA weather station dataset. https://registry.opendata.aws/noaa-ghcnh/

Apparently, if I omit the wildcard, it will match results: ``` curl -sS 'https://127.0.0.1/api/v2/s1?token=MYAWESOMETOKEN&q=NAME:BANAK' | jq .total 18716 ``` This result set happens to match the result set when querying...

Or as described in the Spark documentation, we should allow the use of the default namespace if an explicit namespace is not provided. And use the `default` `ServiceAccount` in the...

Note that at this point, we've added support for namespaces, and the current expectation is that the default serviceaccount for that namespace has all permissions in that namespace.