Skip to content
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

Choosing an encoding does not affect the display of a row key #65

Open
CYarros10 opened this issue Apr 14, 2022 · 0 comments
Open

Choosing an encoding does not affect the display of a row key #65

CYarros10 opened this issue Apr 14, 2022 · 0 comments
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@CYarros10
Copy link

Is your feature request related to a problem? Please describe.
I need to view data that is in bytes. cloud-bigtable-cbt-cli recently merged a PR (#28) that allowed a user to specify the encoding used when displaying byte data. This allows me to properly view the column values, but unfortunately the row key is still encoded in what I believe is UTF-8.

Describe the solution you'd like
I would love to be able to display the column values and the row key with the same encoding.

Describe alternatives you've considered
I've considered making a separate CLI tool that takes a row key and displays the data however I want, but the team loves CBT CLI for all of its other features and does not want to be switching back and forth between a custom CLI tool and CBT CLI.

Additional context

As you can see I can correctly read the column data, but row key (B?G???A?'?8???K?) isn't legible.

Screen Shot 2022-04-14 at 9 13 05 AM

@CYarros10 CYarros10 added priority: p3 Desirable enhancement or fix. May not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. labels Apr 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Development

No branches or pull requests

1 participant