some adjustments!

1) on alter table, set access group for existing column, not part of the 
execution, and goes only by the New add values (OR might as should be to 
set access griou for existing column_family)
hypertable> SELECT columnName1 FROM TableName
rowname    columnName1 value

  Elapsed time:  0.12 s
Avg value size:  5.00 bytes
  Avg key size:  5.00 bytes
    Throughput:  85.88 bytes/s
   Total cells:  1
    Throughput:  8.59 cells/s
hypertable> ALTER TABLE TableName add(  'clumnName2'  MAX_VERSIONS 1,ACCESS 
GROUP NOBLOOMFILTERED bloomfilter="none" (columnName1 ,columnName2));
Error: Hypertable::Exception: Access Group 'NOBLOOMFILTERED' includes 
unknown column family 'columnName1' - HYPERTABLE HQL parse error



2) ./ht shell --- select with the KEYS_ONLY do not return the 
COLUMN_QUALIFIER as part of the key.
     while, the APIs query do!


Thanks,
Kashirin Alex

On Friday, January 17, 2014 2:10:04 PM UTC+2, Alex Kashirin wrote:
>
> Previous log is with CDH4,
> with QFS it is different, Only:
> root@master-hdfs-namenode:/opt/hypertable/current/log# tail 
> Hypertable.Master.log
> host = www-3.hdfs
> public addr = 192.168.3.23:38060
> local addr = 192.168.3.23:55816
> '') returned error 32512
> sh: 1: /opt/hypertable/0.9.7.15/conf/notification-hook.sh: not found
> 1389960407 WARN Hypertable.Master : 
> (/root/src/hypertable/src/cc/Hypertable/Master/Context.cc:83) shell script 
> conf/notification-hook.sh ('/opt/hypertable/
> 0.9.7.15/conf/notification-hook.sh '[Hypertable] Registering server rs5 - 
> www-6.hdfs (192.168.3.26:38060)' 'Registering server rs5
> host = www-6.hdfs
> public addr = 192.168.3.26:38060
> local addr = 192.168.3.26:58326
> '') returned error 32512
>
>
> The hadoop is not in Safe-Mode!
> Thanks,
> Kashirin Alex
>
> On Friday, January 17, 2014 1:45:07 PM UTC+2, Alex Kashirin wrote:
>>
>> can the upgrade of "Moved sys/RS_METRICS reading code to 
>> Hypertable/Lib/RS_METRICS"
>>
>> be a failure of the follow errors, Master Log:
>> *LOG - AFTER cap cleandb and cap start:*
>> root@master-hdfs-namenode:/opt/hypertable/current/log# tail 
>> Hypertable.Master.log
>> workers=100
>> sh: 1: /opt/hypertable/0.9.7.15/conf/notification-hook.sh: not found
>> 1389958854 WARN Hypertable.Master : 
>> (/root/src/hypertable/src/cc/Hypertable/Master/Context.cc:83) shell script 
>> conf/notification-hook.sh ('/opt/hypertable/
>> 0.9.7.15/conf/notification-hook.sh '[Hypertable] Registering server rs1 
>> - master-hdfs-namenode.hdfs (192.168.0.200:38060)' 'Registering server 
>> rs1
>> host = master-hdfs-namenode.hdfs
>> public addr = 192.168.0.200:38060
>> local addr = 192.168.0.200:52346
>> '') returned error 32512
>> 1389958855 FATAL Hypertable.Master : execute 
>> (/root/src/hypertable/src/cc/Hypertable/Master/OperationInitialize.cc:137): 
>> Problem loading ROOT range - Hypertable::Exception: Problem loading range 
>> 0/0[(null)..0/0:��] in rs1 - COMM broken connection
>> at void 
>> Hypertable::Utility::create_table_load_range(Hypertable::ContextPtr&, const 
>> Hypertable::String&, Hypertable::TableIdentifier&, Hypertable::RangeSpec&, 
>> bool) (/root/src/hypertable/src/cc/Hypertable/Master/Utility.cc:329)
>> at void Hypertable::RangeServerClient::do_load_range(const 
>> Hypertable::CommAddress&, const Hypertable::TableIdentifier&, const 
>> Hypertable::RangeSpec&, const Hypertable::RangeState&, bool, uint32_t) 
>> (/root/src/hypertable/src/cc/Hypertable/Lib/RangeServerClient.cc:136): 
>> RangeServer load_range() failure : Event: type=ERROR "COMM broken 
>> connection" from=192.168.0.200:52346
>> root@master-hdfs-namenode:/opt/hypertable/current/log# tail 
>> Hypertable.Master.log
>> workers=100
>> sh: 1: /opt/hypertable/0.9.7.15/conf/notification-hook.sh: not found
>> 1389958854 WARN Hypertable.Master : 
>> (/root/src/hypertable/src/cc/Hypertable/Master/Context.cc:83) shell script 
>> conf/notification-hook.sh ('/opt/hypertable/
>> 0.9.7.15/conf/notification-hook.sh '[Hypertable] Registering server rs1 
>> - master-hdfs-namenode.hdfs (192.168.0.200:38060)' 'Registering server 
>> rs1
>> host = master-hdfs-namenode.hdfs
>> public addr = 192.168.0.200:38060
>> local addr = 192.168.0.200:52346
>> '') returned error 32512
>> 1389958855 FATAL Hypertable.Master : execute 
>> (/root/src/hypertable/src/cc/Hypertable/Master/OperationInitialize.cc:137): 
>> Problem loading ROOT range - Hypertable::Exception: Problem loading range 
>> 0/0[(null)..0/0:��] in rs1 - COMM broken connection
>> at void 
>> Hypertable::Utility::create_table_load_range(Hypertable::ContextPtr&, const 
>> Hypertable::String&, Hypertable::TableIdentifier&, Hypertable::RangeSpec&, 
>> bool) (/root/src/hypertable/src/cc/Hypertable/Master/Utility.cc:329)
>> at void Hypertable::RangeServerClient::do_load_range(const 
>> Hypertable::CommAddress&, const Hypertable::TableIdentifier&, const 
>> Hypertable::RangeSpec&, const Hypertable::RangeState&, bool, uint32_t) 
>> (/root/src/hypertable/src/cc/Hypertable/Lib/RangeServerClient.cc:136): 
>> RangeServer load_range() failure : Event: type=ERROR "COMM broken 
>> connection" from=192.168.0.200:52346
>>
>> *LOG, After cap stop and cap start:*
>> root@master-hdfs-namenode:/opt/hypertable/current/log# tail 
>> Hypertable.Master.log
>> keepalive=30000
>> lease-interval=1000000
>> logging-level=warn
>> pidfile=/opt/hypertable/current/run/Hypertable.Master.pid
>> port=38050
>> reactors=1
>> verbose=true
>> workers=100
>> 1389958927 ERROR Hypertable.Master : main 
>> (/root/src/hypertable/src/cc/Hypertable/Master/main.cc:384): 
>> Hypertable::Exception: sys/RS_METRICS - HYPERTABLE table does not exist
>> at void Hypertable::Table::initialize() 
>> (/root/src/hypertable/src/cc/Hypertable/Lib/Table.cc:98)
>>
>>
>> Thanks,
>> Kashirin Alex
>>
>> On Thursday, January 16, 2014 7:15:36 PM UTC+2, Doug Judd wrote:
>>>
>>> Yes, this release includes a fix for issue 
>>> 1159<https://code.google.com/p/hypertable/issues/detail?id=1159>. 
>>>  If you're running on top of the local filesystem (e.g. not HDFS), setting 
>>> the DfsBroker.Local.DirectIO property to *true* can give you better 
>>> performance because it avoids the double-caching problem of having the same 
>>> data cached both within the RangeServer and the OS.  The last two items are 
>>> just internal things that don't have any user facing impact.
>>>
>>> - Doug
>>>
>>>
>>> On Mon, Jan 13, 2014 at 6:23 AM, Alex Kashirin <[email protected]>wrote:
>>>
>>>> some questions:
>>>>
>>>> "Fixed QFS Broker" - is the hint files issue fixed as well?
>>>>
>>>> "DfsBroker.Local.DirectIO" --- IS THAT GOOD ONLY to fs blocks located 
>>>> on the RS machine?
>>>>
>>>> "issue1063: Made Defects-issue783-offload1 test more robust" -- At the 
>>>> ranges count get to zero(after several offload executions), the command 
>>>> should as well shut-down the RS , should it? (
>>>> https://groups.google.com/forum/#!searchin/hypertable-user/offload/hypertable-user/iRf1cIbHHPQ/zcHMDXnJzRgJ
>>>> )
>>>>
>>>> "Moved sys/RS_METRICS reading code to Hypertable/Lib/RS_METRICS" -- 
>>>> Does that require compete data re-loaded after cleandb?
>>>>
>>>>
>>>> Thanks,
>>>> Kashirin Alex
>>>> On Friday, January 10, 2014 6:29:29 PM UTC+2, Doug Judd wrote:
>>>>>
>>>>> Hypertable version 0.9.7.15 is now available for download  at 
>>>>> http://www.hypertable.com/download/.
>>>>>
>>>>> Version 0.9.7.15:
>>>>> (2014-01-10)
>>>>>
>>>>>     Fixed QFS Broker
>>>>>     issue1159: Fixed CellStoreBlockIndexArray::fraction_covered() bug
>>>>>     Made merging compaction algo more aggressive during low activity 
>>>>> period
>>>>>     Added commons-lang-2.5.jar to fix missing symbol under CDH4.5
>>>>>     Added TimeWindow class for defining low activty window
>>>>>     Prioritize merging compactions ahead of minor compactions
>>>>>     Moved sys/RS_METRICS reading code to Hypertable/Lib/RS_METRICS
>>>>>     Fixed memory alignment issues with DfsBroker.Local.DirectIO=true
>>>>>     Fixed quote trimming problem in HqlParser
>>>>>     issue 1180: Fixed intermittent Client-periodic-flush failure
>>>>>     issue1063: Made Defects-issue783-offload1 test more robust
>>>>>     Throw exceptions in SerializedCellsReader/Writer on empty row key
>>>>>     issue1175: Fixed bug when supplying LIMIT with ROW interval
>>>>> -- 
>>>>> Doug Judd
>>>>> CEO, Hypertable Inc.
>>>>>  
>>>> -- 
>>>> You received this message because you are subscribed to the Google 
>>>> Groups "Hypertable User" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>> an email to [email protected].
>>>> To post to this group, send email to [email protected].
>>>> Visit this group at http://groups.google.com/group/hypertable-user.
>>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>>
>>>
>>>
>>>
>>> -- 
>>> Doug Judd
>>> CEO, Hypertable Inc.
>>>  
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Hypertable Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/hypertable-dev.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to