t> - Cloud Cassandra Hosting*
>
>
> On Thu, 24 Nov 2016 05:38:36 -0500*joseph gao
> >* wrote
>
> Hi，Vladimir,
> I have to do the whole stuff in 2 step. DROP whole keyspace works in
> step2. But in step 1, I have to drop 2000 tables。 All I could wait and ski
ROP whole keyspace an option?
>
> Best regards, Vladimir Yudovin,
> *Winguzone <https://winguzone.com?from=list> - Cloud Cassandra Hosting*
>
>
> On Thu, 24 Nov 2016 03:00:40 -0500*joseph gao
> >* wrote
>
> Hi, all
> I've had a very bad syst
sing
cqlsh or driver client.
So is there an effectively way to drop these unused table ? Thanks very
much.
--
------
Joseph Gao
PhoneNum:18136950721
QQ: 409343351
r:na]
>> at
>> com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2280)
>> ~[guava-16.0.jar:na]
>> at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2195)
>> ~[guava-16.0.jar:na]
>>
>>
>> On Tue, Sep 20, 2
spite saying tcp6 and :::*, it still listens on IPv4.
>>> As far as I'm aware this happens on all 2.1 Cassandra nodes, and may just
>>> be an oddity of netstat. It would be unrelated to your connection timeout
>>> issues, that's most likely related to fir
pens on all 2.1 Cassandra nodes, and may just
> be an oddity of netstat. It would be unrelated to your connection timeout
> issues, that's most likely related to firewall/network issues.
>
> On 9 May 2016 at 09:59, joseph gao wrote:
>
>> It doesn't work ,still usi
eers,
>
> ---
>
> Alain Rodriguez - al...@thelastpickle.com
>
> France
>
> The Last Pickle - Apache Cassandra Consulting
>
> http://www.thelastpickle.com
>
> 2016-03-30 6:09 GMT+02:00 joseph gao :
>
>> why cassandra using tcp6 for 9042
why cassandra using tcp6 for 9042 port like :
tcp6 0 0 0.0.0.0:9042:::*LISTEN
would this be the problem
2016-03-30 11:34 GMT+08:00 joseph gao :
> still have not fixed it . cqlsh: error: no such option: --connect-timeout
> cqlsh version
---
> Alain Rodriguez - al...@thelastpickle.com
> France
>
> The Last Pickle - Apache Cassandra Consulting
> http://www.thelastpickle.com
>
> 2016-03-21 9:59 GMT+01:00 joseph gao :
>
>> cqlsh version 5.0.1. nodetool tpstats looks good, log looks good. And I
>&
Specify the default request timeout in seconds
> (default:
> 10 seconds).
>
> C*heers,
> ---
> Alain Rodriguez - al...@thelastpickle.com
> France
>
> The Last Pickle - Apache Cassandra Consulting
> http://www.thelastpickle.com
>
>
-
> Alain Rodriguez - al...@thelastpickle.com
> France
>
> The Last Pickle - Apache Cassandra Consulting
> http://www.thelastpickle.com
>
> 2016-03-17 14:26 GMT+01:00 joseph gao :
>
>> hi, all
>> cassandra version 2.1.7
>> When I use cqlsh to con
e. Anybody knows
why?
--
--
Joseph Gao
PhoneNum:15210513582
QQ: 409343351
The Last Pickle - Apache Cassandra Consulting
>> http://www.thelastpickle.com
>>
>> 2016-03-17 14:26 GMT+01:00 joseph gao :
>>
>>> hi, all
>>> cassandra version 2.1.7
>>> When I use cqlsh to connect cassandra, something is wrong
>>>
>&g
By the way, when would be the version 2.1.10 published?
2015-12-15 10:02 GMT+08:00 joseph gao :
> That's great. Thanks, Alex!
>
> 2015-10-02 0:36 GMT+08:00 Alexandre Dutra :
>
>> I confirm that the optional schema metadata feature (JAVA-828
>> <https://datastax-o
AVA-420>.
> Until this is not solved, the workaround (and the best practice) is to
> avoid using "SELECT *" statements and explicitly name the columns you need.
>
> Hope that helps,
>
> Alexandre
>
> On Fri, Aug 28, 2015 at 4:58 AM joseph gao wrote:
>
>&g
able the Metadata API
>> http://www.datastax.com/dev/blog/datastax-java-driver-2-0-11-released.
>> I'm not sure at this moment if this has been merged into 2.1 already.
>>
>> On Sun, Sep 20, 2015 at 9:22 AM, joseph gao
>> wrote:
>>
>>> cassand
Hi, anybody could help me?
2015-09-21 0:47 GMT+08:00 joseph gao :
> ps : that's the code in java drive , in MetaData.TokenMap.build:
>
> for (KeyspaceMetadata keyspace : keyspaces)
> {
> ReplicationStrategy strategy = keyspace.replicationStrategy();
> Map> ks
hMap
2015-09-21 0:22 GMT+08:00 joseph gao :
> cassandra: 2.1.7
> java driver: datastax java driver 2.1.6
>
> Here is the problem:
>My application uses 2000+ keyspaces, and will dynamically create
> keyspaces and tables. And then in java client, the
> Metadata.tokenMap.to
rategy and
replicationFactor is 3
So would it be possible if keyspaces use same strategy, the value of
tokenToHost map use a same map. So it would extremely reduce the memory
usage
thanks a lot
--
------
Joseph Gao
PhoneNum:15210513582
QQ: 409343351
if already fixed, my use case is wrong. But I think it's very normal case.
2015-08-28 10:57 GMT+08:00 joseph gao :
> I don't understand, does the issue mean 'don't use wildcard' or 'already
> fixed'?
>
> 2015-08-26 15:16 GMT+08:00 Peer, Oded :
I don't understand, does the issue mean 'don't use wildcard' or 'already
fixed'?
2015-08-26 15:16 GMT+08:00 Peer, Oded :
> See https://issues.apache.org/jira/browse/CASSANDRA-7910
>
>
>
>
>
> *From:* joseph gao [mailto:gaojf.bok...@gmail.com]
Hi, anybody knows how to resolve this problem?
2015-08-23 1:35 GMT+08:00 joseph gao :
>
> I'm using cassandra 2.1.7 and datastax java drive 2.1.6
> Here is the problem:
>
> I use PrepareStatement for query like : SELECT * FROM somespace.sometable
> where id
eStatement.
So it neither re-prepare automatically nor allow user to re-prepare!
Is this a bug or I use it like a fool?
--
------
Joseph Gao
PhoneNum:15210513582
QQ: 409343351
.
>
> There is a reported bug and fixed in 2.1.3. See
> https://issues.apache.org/jira/browse/CASSANDRA-7910
>
>
>
> *From:* joseph gao [mailto:gaojf.bok...@gmail.com]
> *Sent:* Monday, June 15, 2015 10:52 AM
> *To:* user@cassandra.apache.org
> *Subject:* PrepareStatem
mer Cached
PrepareStatement, the metadata will dismatch the data. The metadata tells n
column, and the data tells n+1 column. So what should I do to avoid this
problem?
--
------
Joseph Gao
PhoneNum:15210513582
QQ: 409343351
25 matches
Mail list logo
