Hi,
I am trying to delete a keyspace called Index.
Here is all the versions of the drop I tried.
[default@unknown] drop keyspace 'Index';
Keyspace ''Index'' not found.
[default@unknown] drop keyspace Index;
Syntax error at position 14: mismatched in
The global index JIRA actually mentions compound index but it seems that
there is no JIRA created for this feature? Anyway, I think I should wait
for 3.0 and see what does it bring to index. Thanks.
On Fri, Dec 26, 2014 at 6:09 PM, DuyHai Doan wrote:
> Many JIRA related to index are opened
andard
INFO 16:14:33,615 Sampling index for
C:\var\lib\cassandra\data\system\LocationInfo-1-Data.db
INFO 16:14:33,631 Removing orphan
C:\var\lib\cassandra\data\Lookin2\Users-tmp-27-Index.db
INFO 16:14:33,631 Sampling index for
C:\var\lib\cassandra\data\Lookin2\Users-19-Data.db
INFO 16:14:33,662
rror message is:
INFO 12:46:30,823 Auto DiskAccessMode determined to be standard
INFO 12:46:31,084 Sampling index for
/usr/local/cassandra/data/system/LocationInfo-9-Data.db
INFO 12:46:31,084 Sampling index for
/usr/local/cassandra/data/system/LocationInfo-10-D
e what it is? Details
> below.
>
> Starting Cassandra Server
> Listening for transport dt_socket at address:
> INFO 16:14:33,459 Auto DiskAccessMode determined to be standard
> INFO 16:14:33,615 Sampling index for
> C:\var\lib\cassandra\data\system\LocationInfo-1-Data.db
>
9 Auto DiskAccessMode determined to be standard
>> INFO 16:14:33,615 Sampling index for
>> C:\var\lib\cassandra\data\system\LocationInfo-1-Data.db
>> INFO 16:14:33,631 Removing orphan
>> C:\var\lib\cassandra\data\Lookin2\Users-tmp-27-Index.db
>> INFO 16:14:33,631 Sampl
below.
> >>
> >> Starting Cassandra Server
> >> Listening for transport dt_socket at address:
> >> INFO 16:14:33,459 Auto DiskAccessMode determined to be standard
> >> INFO 16:14:33,615 Sampling index for
> >> C:\var\lib\cassandra\data\s
Many JIRA related to index are opened for 3.x
Global indices: https://issues.apache.org/jira/browse/CASSANDRA-6477
Functional index: https://issues.apache.org/jira/browse/CASSANDRA-7458
Partial index: https://issues.apache.org/jira/browse/CASSANDRA-7391
On Fri, Dec 26, 2014 at 10:49 AM, ziju
Hi all,
We recently went through an upgrade from 0.7.0 to 1.2.13
Everything went well, except for one issue.
We have multiple column families for one keyspace.
Across these CFs there is one column that has the same index key.
The issue is that the index areaManagerId_idx is unique per CF, but
Unfortunately for you, ALTER INDEX does not exist.
And anyway, even if it exists, altering an index option is going likely to
require index rebuild so you can't cut it anyway
On Fri, Mar 4, 2016 at 4:59 PM, Jacques-Henri Berthemet <
jacques-henri.berthe...@genesys.com> wrote:
I don't think compound indexes are going to happen for 3.0. Perhaps 3.1,
but they haven't really been discussed in depth.
On Fri, Dec 26, 2014 at 4:31 AM, ziju feng wrote:
> The global index JIRA actually mentions compound index but it seems that
> there is no JIRA created
Sounds like you had some bad hardware take down your index files.
(Cassandra fsyncs them after writing them and before renaming them to
being live, so if it's missing pieces then it's always been hardware
at fault that I have seen.
You could try rebuilding your index files from the
Creating a secondary index will trigger the build of that index
automatically.
However, that built is done asynchronously and can take some time if you
have lots of existing data to index. To know when that building is done,
you can check the nodes log for an entry looking like "Index bui
Hi,
According to SASI source code (3.11.0) it will always have priority over
regular secondary index:
https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/index/sasi/SASIIndex.java#L234
public long getEstimatedResultRows()
{
// this is temporary
t;> I'm getting an "Expected both token and generation columns; found
>> >> ColumnFamily" error during startup can anyone tell me what it is?
>> >> Details
>> >> below.
>> >>
>> >> Starting Cassandra Server
>> &g
during startup can anyone tell me what it is?
> >> >> Details
> >> >> below.
> >> >>
> >> >> Starting Cassandra Server
> >> >> Listening for transport dt_socket at address:
> >> >> INFO 16:14:33,459 Auto
Listening for transport dt_socket at address:
>> INFO 16:14:33,459 Auto DiskAccessMode determined to be standard
>> INFO 16:14:33,615 Sampling index for
>> C:\var\lib\cassandra\data\system\LocationInfo-1-Data.db
>> INFO 16:14:33,631 Removing orphan
>> C:\var\lib\ca
t;
> >> I'm getting an "Expected both token and generation columns; found
> >> ColumnFamily" error during startup can anyone tell me what it is?
> Details
> >> below.
> >>
> >> Starting Cassandra Server
> >> Listening for transport dt
Hello -
I am using 0.8 Beta 2 and have a CF containing COMPANY, ACCOUNTNUMBER and
some account related data. I have index on both Company and AccountNumber.
If I run a query -
SELECT FROM COMPANYCF WHERE COMPANY='XXX' AND ACCOUNTNUMBER = 'YYY'
Even though ACCOUNTNUM
No, Cassandra uses statistics to see which index will result in less
rows to check.
On Wed, May 11, 2011 at 12:42 PM, Baskar Duraikannu
wrote:
> Hello -
> I am using 0.8 Beta 2 and have a CF containing COMPANY, ACCOUNTNUMBER and
> some account related data. I have index on both Co
Is this a secondary indexer of your own design so that you know that
changing the options will be safe for existing index entries?
It might be worth a Jira.
Otherwise, you may jus have to manually go in and hack the information
under the hood.
-- Jack Krupansky
On Fri, Mar 4, 2016 at 12:14 PM
Thanks,
Apparently for 1.2.5 it did not build automatically. Diescribe shows index[]
which indicates it was not built.
I will try the nodetool command. I dd not see it in the hep list though.
Best Regards,
-Tony
From: Sylvain Lebresne
To: "user@cassandra.apache.org" ; Tony Aneci
If you’re only creating index so that your query work, think again! You’ll be
storing secondary index on each node , queries involving index could create
issues (slowness!!) down the road the when index on multiple node Is involved
and not maintained! Tables involving a lot of inserts/delete
Hey there –
Like other suggested before adding more index , look for opportunity to
de-normalize your data model OR create composite keys for your primary index –
if that works for you.
Secondary index are there so you can leverage them they come with cost. They’re
difficult to manage , as you
Hello,
Before 0.7, actually we can create an extra ColumnFamily as an secondary
index, if we need.
I was wondering whether the secondary index mechanism in 0.7 just likes
creating an extra ColumnFamily as an index.
The difference is only that users don't take care of the maintainence o
No, but I see message of "Creating new index" after most recent restart of
Cassandra which is at 2012-07-18 13:51:37,306.
grep -i "index" /data/cassandra/log/system/system.log.2|grep -v IndexInfo
INFO [main] 2012-07-18 13:53:49,398 DatabaseDescriptor.java (line 170)
:44,893
AbstractSimplePerColumnSecondaryIndex.java (line 118) applying index row
1 in ColumnFamily(DRDevices.DRDevices_touchscreen_idx
[416e64726f69645f48494c4956455f48493453:false:0@1366633655364522,])
DEBUG [MutationStage:117] 2013-04-23 06:23:44,893
AbstractSimplePerColumnSecondaryIndex.java
In the original source code Sasi will be chosen instead of secondary index
Le 12 juil. 2017 09:13, "Vlad" a écrit :
> Hi,
>
> it's possible to create both regular secondary index and SASI on the same
> column:
>
>
>
>
> *CREATE TABLE ks.tb (id int PR
Compound index in MongoDB is really useful for qiery that involves
filtering/sorting on multiple columns. I was wondering if Cassandra 3.0 is
supposed to implement this feature.
When I read through JIRA, I only found feature like CASSANDRA-6048
<https://issues.apache.org/jira/browse/CASSAN
Index updates require read-before-write (to find out what the prior
version was, if any, and update the index accordingly). This is
random i/o.
Index creation on the other hand is a lot of sequential i/o, hence
more efficient.
So, the classic bulk load advice to ingest data prior to creating
Indeed it’s a custom implementation of PerRowSecondaryIndex, in my case I know
it’s safe to update the particular setting I want update, and it won’t rebuild
the index, just provide the ability to tune some settings.
Even on regular Cassandra indexes that are based on SSTables you could want to
DROP and re-create the index with the new options
On Fri, Mar 4, 2016 at 3:45 PM, Jacques-Henri Berthemet <
jacques-henri.berthe...@genesys.com> wrote:
> Hi,
>
>
>
> I’m using Cassandra 2.2.5 with a custom secondary index. It’s created with
> the below syntax:
>
>
Hello
We started using cassandra at version 0.7, which allowed duplicate
names for indexes. We upgraded to version 0.8.10 a while ago and
everything has been working fine. Now I am not able to run 'update
column family' on CF with duplicate index names with other CFs.
If I update t
Hi,
I'm trying to add a new secondary index on a CF which already have a secondary
index by calling "update column family".
But the CF was left with just the new secondary index and the old index
disappeared. AFAIK, the only way to keep both indices was to include the old
sec
,
STUDENT.STUDENT_ROLL_NUMBER_idx, STUDENT.STUDENT_SEMESTER_idx,
STUDENT.STUDENT_STUDENT_NAME_idx, STUDENT.STUDENT_UNIQUE_ID_idx]
Column Metadata:
Column Name: PERCENTAGE
Validation Class: org.apache.cassandra.db.marshal.FloatType
Index Name: STUDENT_PERCENTAGE_idx
Index
to make it work (which didn't happen, though ;-) )
because my secondary index was returning wrong results and I wasn't able
to rebuild it.
However, I can't tell for sure that no-one else has ever modified it
using CQL before.
Can you provide the schema after the update and
Krupansky
On Wed, Dec 31, 2014 at 11:29 AM, Tyler Hobbs wrote:
> I don't think compound indexes are going to happen for 3.0. Perhaps 3.1,
> but they haven't really been discussed in depth.
>
> On Fri, Dec 26, 2014 at 4:31 AM, ziju feng wrote:
>
>> The global index
Hi,
it's possible to create both regular secondary index and SASI on the same
column:
CREATE TABLE ks.tb (id int PRIMARY KEY, name text);
CREATE CUSTOM INDEX tb_name_idx_1 ON ks.tb (name) USING
'org.apache.cassandra.index.sasi.SASIIndex';
CREATE INDEX tb_name_idx ON ks.tb (nam
Hi All,
I updated a table with a secondary index. I discovered using CLI describe that
the index was not built.
How do I build an index after I have altered an existing table with data?
I looked at nodetool and cli and saw no command that had the word build index
associated with it. And most
Hello Robert
There are some maths involved when considering the performance of
secondary index in C*
First, the current implementation is a distributed 2nd index, meaning that
each node that contains actual data also contains the index data.
So considering a cluster of *N* nodes with
12 AM
Subject: Re: How to build indexes?
Creating a secondary index will trigger the build of that index automatically.
However, that built is done asynchronously and can take some time if you have
lots of existing data to index. To know when that building is done, you can
check the nodes log
On Mon, May 19, 2014 at 6:39 AM, mahesh rajamani
wrote:
> Sorry I just realized the table name in 2 schema are slightly different,
> but still i am not sure why i should not use same index name across
> different schema. Below is the instruction to reproduce.
>
>
> Create
;
> DEBUG [MutationStage:110] 2013-04-23 06:23:44,893
> AbstractSimplePerColumnSecondaryIndex.java (line 118) applying index row 1 in
> ColumnFamily(DRDevices.DRDevices_touchscreen_idx
> [416e64726f69645f48494c4956455f48493453:false:0@1366633655364522,])
> DEBUG
I did a insertion test with and without secondary indexes, and found that:
Without secondary index: ~10864 rows inserted per second
With secondary index on one column(BytesType): ~1515 rows inserted per
second
Is this normal? why secondary index would have so much affect?
I noticed that If I
Can I drop composite index in CLI? What’s syntax? Or do I have to use cqlsh?
[default@mobilelogks] drop index on
MobilePushNotificationLog.retryCount;
Column 'retryCount' does
not have an index.
[default@mobilelogks] help drop index;
drop index on .;
Drops index on specified
> That is a good reason for both to be configurable IMO.
index sampling is currently configurable only per node, it would be
better to have it per Keyspace because we are using OLTP like and OLAP
keyspaces in same cluster. OLAP Keyspaces has about 1000x more rows.
But its difficult
is indexed column as I said above.
Could you please tell me the performance difference btwn above 2 queries.
Thanks in advance,
Techpyaasaa
On Tue, Jun 20, 2017 at 9:03 PM, ZAIDI, ASAD A wrote:
> Hey there –
>
>
>
> Like other suggested before adding more index , look for oppo
Dear All,
We met some C* nodes oom during secondary index creation with C* 2.1.18.
As per https://issues.apache.org/jira/browse/CASSANDRA-12796,the flush writer
will be blocked by index rebuild.but we still have some confusions:
1.not sure if secondary index creation is the same as index
contd..
when can the discrepancy in the index arise. Any specific example?
I can not pin point any exact situation. I was referring to situations
which can hamper data replication, consistency adversely. e.g. single or
multiple Node failures/recovery
anything specific to stratio-lucene-index
I have a three-node cluster running Cassandra 1.0.10. In this cluster
is a keyspace with RF=3. I *updated* a column family via Astyanax to
add a column definition with an index on that column. Then I ran a
backfill to populate the column in every row. Then I tried to query
the index from Java
Sorry I just realized the table name in 2 schema are slightly different,
but still i am not sure why i should not use same index name across
different schema. Below is the instruction to reproduce.
Created 2 keyspace using cassandra-cli
[default@unknown] create keyspace keyspace1 with
Why indexing BLOB data ? It does not make any sense
"I thought sasi index is globally held, in contrast to the normal secondary
index.." --> Who said that ? It's just wrong
On Thu, Feb 16, 2017 at 1:50 PM, Micha wrote:
> Hi,
>
>
> my table has (among others) t
this doesn't make so much difference to the above queries), the indexes
are sorted by primary key of the rows they refer to. So the more of the
primary key you specify in the query, the more targeted the index lookup
becomes.
On 25 June 2017 at 16:18, techpyaasa . wrote:
> Thanks for the
Hello,
As mentioned by Ed Anuff in his blog and slides, one way to build customized
secondary index is:
We use one CF, each row to represent a secondary index, with the secondary
index name as row key.
For example,
Indexes = {
"User_Keys_By_Last_Name" : {
"adams" :
a good idea to manage one with the other)
Yes, I know - I only tried using CQL after I realized that CLI is not
working, as I had to make it work (which didn't happen, though ;-) )
because my secondary index was returning wrong results and I wasn't able
to rebuild it.
However, I can'
Hi
Could you help modelling this usecase
I have below table ..I will update tagid's columns set(bigit) based on
PK. I have created the secondary index column on tagid to query like below..
Select * from keyspace.customer_sensor_tagids where tagids CONTAINS
11358097;
this query is
On Thu, Aug 23, 2012 at 6:54 PM, Richard Crowley wrote:
> I have a three-node cluster running Cassandra 1.0.10. In this cluster
> is a keyspace with RF=3. I *updated* a column family via Astyanax to
> add a column definition with an index on that column. Then I ran a
> backfill to
Let me rephrase. I am talking about the index file on disk created per sstable.
Does that contain all key indexes?
Sent from Samsung mobile
Robert Coli wrote:
On Fri, Apr 19, 2013 at 10:38 AM, Kanwar Sangha wrote:
> Guys – Quick question. The index filter file created for a sstable conta
Yes, that is a known weakness of the current cli interface to column_metadata.
On Wed, Feb 16, 2011 at 3:16 PM, Yueyu Fu wrote:
> Hi,
>
> I'm trying to add a new secondary index on a CF which already have a
> secondary index by calling "update column family".
>
&
The row index is an index of the columns stored in a particular row: it is
only written when a row gets larger than column_index_size_in_kb (see your
config file). The sstable index is currently an index of the keys stored in
an sstable, but #2319 proposes to merge the sstable and row indexes.
On
Hi,
I had Cassandra version 0.7.6 and a schema called Index.
When I upgraded to 1.0.3 I realized that I cant create this keyspace maybe
because Index has become a reserved word?
I tried 'Index' and "Index" and still get an error so I created a new
keyspace instead.
from index_entries for user U0
4 ) B(T2) deletes previous location (T0,L0) from index_entries for user U0
5 ) A(T1) deletes previous location (L0,T0,U0) for user U0 from index
6 ) B(T2) deletes previous location (L0,T0,U0) for user U0 from index
7 ) A(T1) inserts new location (T1,L1) into index_entries for
It’s not possible, it’s a PerRowSecondary index, potentially as big as the
table itself (few TBs) it will take a very long time to drop and re-create.
--
Jacques-Henri Berthemet
From: DuyHai Doan [mailto:doanduy...@gmail.com]
Sent: vendredi 4 mars 2016 14:52
To: user@cassandra.apache.org
On Tue, Aug 23, 2011 at 10:03 AM, Alvin UW wrote:
> Hello,
>
> As mentioned by Ed Anuff in his blog and slides, one way to build customized
> secondary index is:
> We use one CF, each row to represent a secondary index, with the secondary
> index name as row key.
> For
create an extra ColumnFamily as an secondary
> index, if we need.
>
> I was wondering whether the secondary index mechanism in 0.7 just likes
> creating an extra ColumnFamily as an index.
> The difference is only that users don't take care of the maintainence of
> the secondar
-Index.db components only contain the index.
In v1.2+ -Summary.db contains a sampling of the index read at startup.
Cheers
-
Aaron Morton
Freelance Cassandra Developer
New Zealand
@aaronmorton
http://www.thelastpickle.com
On 3/02/2013, at 11:03 AM, Kanwar Sangha wrote:
>
Hello,
We have been noticing an issue where, about 50% of the time in which a node
fails or is restarted, secondary indexes appear to be partially lost or
corrupted. A drop and re-add of the index appears to correct the issue. There
are no errors in the cassandra logs that I see. Part of
Validation Class: org.apache.cassandra.db.marshal.BytesType
Index Name: events_Firm_idx
Index Type: KEYS
Column Name: OrdType
Validation Class: org.apache.cassandra.db.marshal.BytesType
Index Name: events_OrdType_idx
Index Type: KEYS
I finally got the math right for the partition index after tracing through
SSTableWriter.IndexWriter.append(DecoratedKey key, RowIndexEntry
indexEntry). I should also note that I am working off of the source for
1.2.9. Here is the break down for what gets written to disk in the append()
call (my
Hello
Cassandra 1.0.7
Some time ago we used secondary index on one of CF. Due to performance
reasons we dropped this secondary index after while. But now, each time
I add and bootstrap new node I see how cassandra again build this
secondary index on this node (which takes huge time), and
oo like
select * from ks1.cf1 where id1=123 and status=0;
How can I achieve this w/o secondary index (on 'status' column )??
On Tue, Jun 20, 2017 at 12:09 AM, ZAIDI, ASAD A wrote:
> If you’re only creating index so that your query work, think again!
> You’ll be storing secondary i
I am struggling with getting secondary indexes to work. I have created
secondary indexes on some fields that are part of the compound primary key
but only one of the indexes seems to work (the one set on the field 'e' on
the table definition below). Using any other secondary index
> dropped this secondary index after while.
I assume you use UPDATE COLUMN FAMILY in the CLI.
> How can I avoid this secondary index building on node join?
Check the schema using show schema in the cli.
Check that all nodes in the cluster have the same schema, using describe
cluster
Yes, this is what I am worrying about.
2011/8/24 Ryan King
> On Tue, Aug 23, 2011 at 10:03 AM, Alvin UW wrote:
> > Hello,
> >
> > As mentioned by Ed Anuff in his blog and slides, one way to build
> customized
> > secondary index is:
> > We use one CF, eac
U0) for user U0 from index
6 ) B(T2) deletes previous location (L0,T0,U0) for user U0 from index
7 ) A(T1) inserts new location (T1,L1) into index_entries for user U0
8 ) B(T2) inserts new location (T2,L2) into index_entries for user U0
9 ) index_entries for user U0 now contains (T1,L1),(T2,L2)
10
,
STUDENT.STUDENT_PERCENTAGE_idx, STUDENT.STUDENT_ROLL_NUMBER_idx,
STUDENT.STUDENT_SEMESTER_idx, STUDENT.STUDENT_STUDENT_NAME_idx,
STUDENT.STUDENT_UNIQUE_ID_idx]
Column Metadata:
Column Name: PERCENTAGE
Validation Class: org.apache.cassandra.db.marshal.FloatType
Index
Your question is missing a "what". What do you want to know the default of?
If you are asking for the key_validation_class of the Index CF, then it's
the column type that defines it. If you're asking about the index CF
comparator, then in that example it would use a compar
On Fri, Apr 19, 2013 at 10:38 AM, Kanwar Sangha wrote:
> Guys – Quick question. The index filter file created for a sstable contains
> all keys/index offset for a sstable ? I know that when we bring up the node,
> it reads a sample of the keys from this file. So this file contains all k
[1] i'm not particularly worried about transient conditions so that's
ok. i think there's still the possibility of a non-transient false
positive...if 2 writes were to happen at exactly the same time (highly
unlikely), eg
1) A reads previous location (L1) from index ent
Hi,
when can the discrepancy in the index arise. Any specific example?
any documentation which says the index automatically rebuilds/keeps itself
> up to date after updations and deletions
I was unable to locate anything saying this in Apache C* docs. But here is
Datastax link if that
> As I understand from the link below, burning column index-info onto the
> sstable index files will not only eliminate sstables but also reduce disk
> seeks from 3 to 2 for wide rows.
Yes.
> Shouldn't we be wary of the spike in heap usage by promoting column indexes
> to in
Hi,
I'm attempting to build an index on a column acting as part of a composite
key.
This is what I have so far:
CREATE TABLE userinfo2 (
campaignId int,
TS timestamp,
somevalue text,
PRIMARY KEY (campaignId, TS)
);
INSERT INTO userinfo2 (campaignI
Hi,
On Feb 21, 2013, at 7:52 , Kanwar Sangha wrote:
> Hi – Can someone explain the worst case IOPS for a read ? No key cache, No
> row cache, sampling rate say 512.
>
> 1) Bloom filter will be checked to see existence of key (In RAM)
> 2) Index filer sample (IN RAM)
Nice work John. If you learn any more, please share.
S
On Sat, Dec 7, 2013 at 11:50 AM, John Sanda wrote:
> I finally got the math right for the partition index after tracing through
> SSTableWriter.IndexWriter.append(DecoratedKey key, RowIndexEntry
> indexEntry). I should also note
When executing a query like:
get events WHERE Firm=434550 AND ds_timestamp>=1341955958200 AND
ds_timestamp<=1341955958200;
what the 2ndary index implementation will do is:
1) it queries the index for Firm for the row with key 434550 (because
that's the only one restricted by an equal
On Mon, Jun 6, 2011 at 6:28 AM, Donal Zang wrote:
> Another thing I noticed is : if you first do insertion, and then build the
> secondary index use "update column family ...", and then do select based on
> the index, the result is not right (seems the index is still being
Thanks Kurt.
-- --
??: "kurt";;
: 2018??1??11??(??) 11:46
??: "User";
: Re: secondary index creation causes C* oom
1.not sure if secondary index creation is the same as index rebuild
Fairly sure they
Any way I was able to delete the keyspace using python pycassa
Thanks
Michael
From: aaron morton [mailto:aa...@thelastpickle.com]
Sent: Monday, December 19, 2011 9:39 PM
To: user@cassandra.apache.org
Subject: Re: Drop schema Called "Index"
Which keyspace are you trying
Hi,
This looks good but when can the discrepancy in the index arise. Any
specific example?
Is there any documentation which says the index automatically
rebuilds/keeps itself up to date after updations and deletions. Also if
there anything specific to stratio-lucene-index.
Regards
Akshit Jain
On 02/22/2013 07:47 PM, aaron morton wrote:
dropped this secondary index after while.
I assume you use UPDATE COLUMN FAMILY in the CLI.
yes
How can I avoid this secondary index building on node join?
Check the schema using show schema in the cli.
I see no indexes for CF in show schema
IMHO it's only a scalability problem if those nodes have trouble handling the
throughput. The load will go all all replicas, not one, unless you turn off
Read Repair.
If it is a problem then you could manually partition the index into multiple
rows, bit of a pain thought. I'd wait a
Thanks.
2011/8/24 aaron morton
> IMHO it's only a scalability problem if those nodes have trouble handling
> the throughput. The load will go all all replicas, not one, unless you turn
> off Read Repair.
>
> If it is a problem then you could manually partition the index
I am looking into the C* secondary index feature so that I could query the
rows based on the column value. In my use case, I wanted to create index of
several columns or maybe all columns of a row. (A single row does not have
many columns, maybe around 50 - 100 columns) and was looking into
noticing an issue where, about 50% of the time in which a node
> fails or is restarted, secondary indexes appear to be partially lost or
> corrupted. A drop and re-add of the index appears to correct the issue.
> There are no errors in the cassandra logs that I see. Part of the in
Hello,
I have a few questions about secondary indexes.
1st Question:
Quoting this FAQ: https://wiki.apache.org/cassandra/SecondaryIndexes
Q: When you write a new row, when/how does the index get updated? What I
> would like to know is the atomicity of the operation--is the "ind
So when using Redis, how do you go about updating the index?
Do you serialize changes to the index i.e. when someone votes, you then
update the index?
Little confused as to how to go about updating a huge index.
Say you have 1 million stores, and you want to order by the top votes, how
would
Great articles, I did not find those before !
*
SSTable Index - yes I mean column Index.
*I would like to understand, how many disk seeks might be required to find
column in single SSTable.
I am assuming positive bloom filter on row key. Now Cassandra needs to find
out whenever given SSTable
Why are you keeping all your indexes in the same row? We do a similar thing
(maintain several indexes over the same data) and we just have an index column
family with keys like "dest192.168.0.1" which means destination index of
192.168.0.1. You can do rows like User_Keys_By_Last_Name
Thanks.
Assume I use this approach, use the last names as the row keys of secondary
index, and use the base column family key as the column name.
There may be duplication key issue. We may solve it by composite key, like
"adams_1" , "adams_2".
Then, we can query these index by
age one with the other)
>>
>> Yes, I know - I only tried using CQL after I realized that CLI is not
>> working, as I had to make it work (which didn't happen, though ;-) )
>> because my secondary index was returning wrong results and I wasn't able
>> to rebuild
1 - 100 of 2133 matches
Mail list logo
