Cheyene, with Phoenix 4.10, column mapping feature is enabled by default which means the column names declared in the Phoenix schema are going to be different from the column qualifiers in hbase. If you would like to disabled column mapping, set COLUMN_ENCODED_BYTES=NONE property in your ddl.
On Mon, Jun 5, 2017 at 1:09 PM, Cheyenne Forbes < [email protected]> wrote: > Can anyone please help? > > > On Sat, Jun 3, 2017 at 8:51 PM, Cheyenne Forbes < > [email protected]> wrote: > >> I am doing some analytics which require me to scan through a phoenix >> created table with hbase instead of a phoenix select query. >> >> I created a column with the name 'fname' but a scan with hbase shell >> shows "\x80\x0F": >> >> \x00\x00Z\xF3\x10z@\x14 column=PERSONAL:\x80\x0F, >> timestamp=1496360923816, value=Cheyenne >> >> How can I scan using column names if for example the name i gave is >> "fname" but in hbase I it is "\x80\x0F"? >> >> Regards, >> >> Cheyenne O. Forbes >> > >
