Skip to content
This repository has been archived by the owner. It is now read-only.

Ensure that all Cassandra queries can run #73

Merged
merged 1 commit into from Jul 7, 2017

Conversation

Projects
None yet
2 participants
@c-w
Copy link
Member

commented Jul 7, 2017

Implementation is terrible, but this is likely the best we can do with the current schema.

@jcjimenez
Copy link
Contributor

left a comment

I think this will work as long as we have a very small number of records.

params.push(pipeline);
}

let query = `SELECT detectedkeywords FROM fortis.events WHERE ${clauses.join(' AND ')} ALLOW FILTERING`;

This comment has been minimized.

Copy link
@jcjimenez

jcjimenez Jul 7, 2017

Contributor

ALLOW FILTERING ouch!

This comment has been minimized.

Copy link
@c-w

c-w Jul 7, 2017

Author Member

Yes, the schema right now requires us to do this :( We really have to formulate the v2 queries that we want and make sure that the DB schema supports them. Adding @erikschlegel for visibility.


const query = `SELECT * FROM fortis.events WHERE (${clauses.join(' AND ')})`;
const query = `SELECT * FROM fortis.events WHERE ${clauses.join(' AND ')} ALLOW FILTERING`;

This comment has been minimized.

Copy link
@jcjimenez

jcjimenez Jul 7, 2017

Contributor

Another ouch. AFAIK, ALLOW FILTERING fetches everything and does driver-side filtering, right?

This comment has been minimized.

Copy link
@c-w

c-w Jul 7, 2017

Author Member

@c-w c-w merged commit cb44b1c into master Jul 7, 2017

2 checks passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
continuous-integration/travis-ci/push The Travis CI build passed
Details

@c-w c-w deleted the cassandra-limitations branch Jul 7, 2017

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.