I've tried: "\x00\x00\x00\x12d\xF47\x9F" "\\x00\\x00\\x00\\x12d\\xF47\\x9F"
"\x00\x00\x00\x12d\xF47\x9F".to_java_bytes "\\x00\\x00\\x00\\x12d\\xF47\\x9F".to_java_bytes no luck :( 2014-10-04 15:58 GMT+04:00 Serega Sheypak <[email protected]>: > Hm... what is the rgiht way to esacape these binary keys? > Tble is not created and there is no exceptions. > > 2014-10-04 15:52 GMT+04:00 Serega Sheypak <[email protected]>: > >> Ok, I got it. Will try. >> >> 2014-10-04 15:46 GMT+04:00 Jean-Marc Spaggiari <[email protected]>: >> >>> Hi Serega, you can not do it that way. The alter will not read this >>> parameter. This should be passed to the create table command instead, or >>> you need to you the split command to split a single region. >>> >>> JM >>> >>> 2014-10-04 7:41 GMT-04:00 Serega Sheypak <[email protected]>: >>> >>> > Hi, I did pick long as a key for hbase table row. >>> > So I see hex string representing my long key in OLD table. >>> > I want to use these split keys as pre-splits for a NEW table which is >>> > EMPTY. >>> > I would like to run a script using hbase shell: >>> > >>> > >>> > disable 'my_new_empty_table_with_long_key' >>> > >>> > alter 'my_table_my_new_empty_table_with_long_keywith_long_jey', NAME => >>> > 's',SPLITS => >>> > ["\\x00\\x00\\x00\\x12d\\xF47\\x9F","\\x00\\x00\\x00\\x12e\\x0D\\xB1N"] >>> > >>> > enable 'my_new_empty_table_with_long_key' >>> > exit >>> > >>> > I run it but nothing happens, splits do not appear. in new table. I >>> ca't >>> > find any errors in region server log which hosts default single region >>> of >>> > table. >>> > >>> >> >> >
