feat: allow set value as BigEndian Int64 #83
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.
Is your feature request related to a problem? Please describe.
from https://github.com/googleapis/cloud-bigtable-cbt-cli/pull/28/files,
cbt read
andcbt lookup
is able to decode BigEndian Int64 with a format file.BigEndian Int64 and UTF8 string are two popular value types. However,
cbt set
still only able to set value as UTF8 string.Describe the solution you'd like
similar to
cbt read
orcbt lookup
, we can improvecbt set
to support format file and encode properly.Describe alternatives you've considered
If it is easy to generalize, it would be nice if
cbt set
can also support full data types, e.g. Hexadecimal, JSON, ProtobufAdditional context
cbt
was quite useful in setup instance/table/column_family in Bigtable emulator (used in development or test environment). I have seen a lot use cases where producer and consumer are different applications and mostly implement in different languages.
since
cbt
is not able to set BigEndian Int64, currently a workaround is to use client SDK to mock data in CI of Consumer applications. It would be more convenient ifcbt set
can alsoThe text was updated successfully, but these errors were encountered: