-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider enforcing no leading underscore in tag keys #11961
Comments
This was resolved via #12391 |
at least, |
influxdb/storage/readservice/cursor.go Lines 143 to 153 in 530ceb9
|
@zhulongcheng thanks for the issue! Hmm I think this is an issue in the read side. @stuartcarnie can you take a look? |
@e-dard the issue I see here is that
which should never be allowed. When a read occurs, the influxdb/storage/readservice/cursor.go Lines 143 to 153 in 530ceb9
|
@stuartcarnie yeah seems about right. I think then we’ll have to check and block these. I’ll put this on the back log. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
don't close. |
Could this be done at the API layer? Would internal calls use the same APIs and so be rejected? |
I would like to consider ensuring that the storage engine does not accept any tag keys with leading underscores, essentially leaving the
_
prefix as a private key space for internal series key information.With that as an invariant, we could make certain performance improvements around reading and parsing keys.
The text was updated successfully, but these errors were encountered: