fix(v1): correct spec typos and KILL QUERY placeholder in v1.12.3 docs

[Copilot]

Addresses several documentation errors in the InfluxDB v1 and Enterprise v1 spec pages introduced in the v1.12.3 release PR.

Changes

• InfluxQL spec typo (both products): Fix "retention polices" → "retention policies" in the regular expressions callout note
• KILL QUERY placeholder (influxdb/v1): Fix inconsistency between syntax example (<qid>) and grammar/prose (query_id) — now uses <query_id> throughout

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

[Copilot]

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• influxdata.github.io
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[jstirnaman]

In InfluxQL, the with_key_clause is a required clause used in SHOW TAG VALUES (and related cardinality) statements to specify which tag key(s) to target. Its syntax is defined as:

with_tag_clause = "WITH KEY" ( "=" tag_key | "!=" tag_key | "=~" regex_lit | "IN (" tag_keys ")" )

[InfluxQL spec]

It supports the following operators:

• = — equal to a specific tag key
• != — not equal to a specific tag key
• =~ — matches a regular expression
• IN (...) — matches any of a list of tag keys

Examples

-- Show all tag values for the "region" tag key
SHOW TAG VALUES WITH KEY = "region"

-- Show tag values for region & host tag keys where service = 'redis'
SHOW TAG VALUES FROM "cpu" WITH KEY IN ("region", "host") WHERE "service" = 'redis'

-- Show tag values for all tag keys that do NOT include the letter "c"
SHOW TAG VALUES WITH KEY !~ /.*c.*/

[SHOW TAG VALUES]

The WITH KEY clause is required for SHOW TAG VALUES queries — without it, the query is invalid. It is also used in cardinality queries such as SHOW TAG VALUES CARDINALITY WITH KEY = "myTagKey". [InfluxQL spec]

[jstirnaman]

In InfluxQL, the with_key_clause is a required clause used in SHOW TAG VALUES (and related cardinality) statements to specify which tag key(s) to target. Its syntax is defined as:

with_tag_clause = "WITH KEY" ( "=" tag_key | "!=" tag_key | "=~" regex_lit | "IN (" tag_keys ")" )

[InfluxQL spec]

It supports the following operators:

• = — equal to a specific tag key
• != — not equal to a specific tag key
• =~ — matches a regular expression
• IN (...) — matches any of a list of tag keys

Examples

-- Show all tag values for the "region" tag key
SHOW TAG VALUES WITH KEY = "region"

-- Show tag values for region & host tag keys where service = 'redis'
SHOW TAG VALUES FROM "cpu" WITH KEY IN ("region", "host") WHERE "service" = 'redis'

-- Show tag values for all tag keys that do NOT include the letter "c"
SHOW TAG VALUES WITH KEY !~ /.*c.*/

[SHOW TAG VALUES]

The WITH KEY clause is required for SHOW TAG VALUES queries — without it, the query is invalid. It is also used in cardinality queries such as SHOW TAG VALUES CARDINALITY WITH KEY = "myTagKey". [InfluxQL spec]

[Copilot]

The spec already defines with_tag_clause with exactly that WITH KEY (...) syntax (line 1274 in the enterprise spec). The references I changed (show_tag_keys_stmt, show_tag_values_cardinality_stmt, show_tag_values_exact_cardinality_stmt) all pointed to with_key_clause, which was never defined — so I updated them to use the defined with_tag_clause production. If a separate with_key_clause production should be added to the grammar, let me know and I can add it.

[jstirnaman]

@copilot revert your clause changes and create a separate issue to research and test them

[Copilot]

Reverted in bcb1d78. I attempted to create a tracking issue via the CLI but lacked the necessary permissions — could you create one, or grant access so I can? The key question to resolve is whether with_key_clause should be replaced with the existing with_tag_clause production (already used by show_tag_values_stmt) or defined separately.

[jstirnaman]

Revert this. The introductory sentence explains why these values are used.

[Copilot]

Reverted in e6ec17e.

[Copilot]

In InfluxQL, the with_key_clause is a required clause used in SHOW TAG VALUES (and related cardinality) statements to specify which tag key(s) to target. Its syntax is defined as:

The clause changes have been reverted in bcb1d78. A separate issue should be created to research whether the undefined with_key_clause references should be aligned with the existing with_tag_clause definition or given their own production.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• https://api.github.com/graphql
  • Triggering command: `/usr/bin/gh gh issue create --repo influxdata/docs-v2 --title docs(v1): research correct production name for WITH KEY clause in InfluxQL spec (with_key_clause vs with_tag_clause) --body ## Background

In the InfluxQL grammar spec for both influxdb/v1 and enterprise_influxdb/v1, the following statements reference with_key_clause:

• show_tag_keys_stmt
• show_tag_values_cardinality_stmt
• `show_tag_values_exact_cardinality_stmt`` (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[github-actions]

Visual Review Skipped

The PR preview deployment did not become available within 10 minutes.
Visual review was skipped. The Copilot code review (Job 2) still ran.

To trigger visual review manually, re-run this workflow after the
preview is deployed.