[Bug] SHOW TIMESERIES WHERE TAGS(...) CONTAINS is Case-Sensitive While Timeseries CONTAINS is Case-Insensitive
- Lingua principale
- Java
- Stelle
- 6.4k
- Fork
- 1.2k
- Merge medio
- 1g 23h
- PR unite (30g)
- 115
Descrizione
### Search before asking
- [x] I searched in the [issues](https://github.com/apache/iotdb/issues) and found nothing similar.
### Version
apache iotdb = 2.0.5
### Describe the bug and provide the minimal reproduce step
I'm encountering inconsistent behavior in SQL queries involving `CONTAINS` filters on timeseries metadata. When searching timeseries by `TAGS`, the `CONTAINS` operator behaves case-sensitively.
```sql
SHOW TIMESERIES WHERE TAGS(description) CONTAINS "Flow";
```
This returns results correctly because one of my timeseries has a tag `description="Flow"`.
But if I change the search to:
```sql
SHOW TIMESERIES WHERE TAGS(description) CONTAINS "flow";
```
It returns no results, even though `"Flow"` exists.
So tag-based `CONTAINS` filtering is case-sensitive.
### What did you expect to see?
`CONTAINS` should behave consistently across metadata fields, ideally being case-insensitive.
For **timeseries names**, the same query type is already **case-insensitive**:
```sql
SHOW TIMESERIES WHERE Timeseries CONTAINS "Flow";
```
This matches `"Flow"`, `"flow"`, `"FLOW"`, etc.
### What did you see instead?
#### Why This Matters:
* TAG searches are commonly used for metadata filtering and discovery.
* Case-sensitive matching makes searching inconsistent with other IoTDB metadata filters.
* It forces users to know exact casing of tags, reducing usability.
### Anything else?
_No response_
### Are you willing to submit a PR?
- [ ] I'm willing to submit a PR!
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Inizia con le query SHOW TIMESERIES nell’issue, confrontando TAGS(description) CONTAINS con Timeseries CONTAINS usando maiuscole e minuscole diverse. Traccia l’implementazione di questi filtri dei metadati e aggiungi la copertura per gli esempi segnalati; il lavoro è completato quando TAGS CONTAINS si comporta in modo coerente con il comportamento esistente di Timeseries CONTAINS, che non distingue tra maiuscole e minuscole.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- java, sql
- Ambito
- databases
- Tipo di issue
- Bug
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 45/100