Re: Hector Problem Basic one

2011-10-12 Thread Wangpei (Peter)
I only saw this error message when all Cassandra nodes are down. How you get the Cluster and how you set the hosts? 发件人: CASSANDRA learner [mailto:cassandralear...@gmail.com] 发送时间: 2011年10月12日 14:30 收件人: user@cassandra.apache.org 主题: Re: Hector Problem Basic one Thanks for the reply ben.

Re: Indexes on heterogeneous rows

2011-04-15 Thread Wangpei (Peter)
Does the get_indexed_slice in 0.7.4 version already do thing that way? It seems always take the 1st indexed column with EQ. Or is it a new feature of coming 0.7.5 or 0.8? -邮件原件- 发件人: Jonathan Ellis [mailto:jbel...@gmail.com] 发送时间: 2011年4月15日 0:21 收件人: user@cassandra.apache.org 抄送: David

Re: result of get_indexed_slices() seems wrong

2011-03-24 Thread Wangpei (Peter)
@cassandra.apache.org 主题: Re: result of get_indexed_slices() seems wrong Looks like this https://issues.apache.org/jira/browse/CASSANDRA-2347 From this discussion http://www.mail-archive.com/user@cassandra.apache.org/msg11291.html Aaron On 24 Mar 2011, at 17:17, Wangpei (Peter) wrote: Hi

result of get_indexed_slices() seems wrong

2011-03-23 Thread Wangpei (Peter)
Hi, This problem occurs when the clause has multi expression and a expression with operator other than EQ. Is anyone meet the same problem? I trace the code, and seen this at ColumnFamilyStore.satisfies() method: int v = data.getComparator().compare(column.value(),

Re: understanding tombstones

2011-03-10 Thread Wangpei (Peter)
My question: what the client would get, when following happens:(RF=3, N=3) 1, write with timestamp T and succeed in all nodes. 2, delete with timestamp T+1, CL=Q, and succeed in node1 and node2 but failed in node3. 3, force flush + compaction 4, read CL=Q Does the client will get the row and

Re: managing a limited-length list as a value

2011-02-19 Thread Wangpei (Peter)
Maybe you can try this: use MAX-time as your column name, then get the first limit columns. -邮件原件- 发件人: Benson Margulies [mailto:bimargul...@gmail.com] 发送时间: 2011年2月19日 2:11 收件人: user@cassandra.apache.org 主题: managing a limited-length list as a value The following is derived from the

Re: Partitioning

2011-02-16 Thread Wangpei (Peter)
I have same question. I read the source code of NetworkTopologyStrategy, seems it always put replica on the first nodes on the ring of the DC. If I am misunderstand, It seems those nodes will became hot spot. Why NetworkTopologyStrategy works that way? is there some alternative can avoid this

Re: time to live rows

2011-02-09 Thread Wangpei (Peter)
AFAIK 2nd index only works for operator EQ. -邮件原件- 发件人: Kallin Nagelberg [mailto:kallin.nagelb...@gmail.com] 发送时间: 2011年2月9日 3:36 收件人: user@cassandra.apache.org 主题: Re: time to live rows I'm thinking if this row expiry notion doesn't pan out then I might create a 'lastAccessed' column

Re: Row Key Types

2011-02-09 Thread Wangpei (Peter)
Did you set compare_with attribute of your ColumnFamily to TimeUUIDType? -邮件原件- 发件人: Bill Speirs [mailto:bill.spe...@gmail.com] 发送时间: 2011年2月2日 0:47 收件人: Cassandra Usergroup 主题: Row Key Types What is the type of a Row Key? Can you define how they are compared? I ask because I'm using

Re: Cassandra + Thrift on RedHat Enterprise 5

2011-01-30 Thread Wangpei (Peter)
Hector document: http://www.riptano.com/sites/default/files/hector-v2-client-doc.pdf 发件人: Vedarth Kulkarni [mailto:vedar...@gmail.com] 发送时间: 2011年1月30日 14:03 收件人: user@cassandra.apache.org 主题: Re: Cassandra + Thrift on RedHat Enterprise 5 How can I use Hector please can you explain me in detail

Re: Schema Design

2011-01-26 Thread Wangpei (Peter)
I am also working on a system store logs from hundreds system. In my scenario, most query will like this: let's look at login logs (category EQ) of that proxy (host EQ) between this Monday and Wednesday(time range). My data model like this: . only 1 CF. that's enough for this scenario. . group

Re: Basic question on a write operation immediately followed by a read

2011-01-24 Thread Wangpei (Peter)
What is the ConsistencyLevel value? Is it ConsistencyLevel.ANY? Javadoc: * Write consistency levels make the following guarantees before reporting success to the client: * ANY Ensure that the write has been written once somewhere, including possibly being hinted in a non-target node.