• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
An Introduction to Distributed Search with Datastax Enterprise Search
 

An Introduction to Distributed Search with Datastax Enterprise Search

on

  • 2,264 views

This is an overview of distributed search with Cassandra and Solr.

This is an overview of distributed search with Cassandra and Solr.

Statistics

Views

Total Views
2,264
Views on SlideShare
1,916
Embed Views
348

Actions

Likes
3
Downloads
15
Comments
0

2 Embeds 348

https://twitter.com 207
http://www.scoop.it 141

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

CC Attribution License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    An Introduction to Distributed Search with Datastax Enterprise Search An Introduction to Distributed Search with Datastax Enterprise Search Presentation Transcript

    • TOO BIGTO FAILAn Introduction to Distributed Search with Cassandra and SolrOpenSource Connections@PatriciaGorlapgorla@o19s.com
    • ABOUT MESystems AnalystProgrammingInformation Retrieval
    • Created at Facebook topower inbox searchDistributed data store runon commodity serversHighly availableNo one single point of failureCASSANDRA
    • WHO USES CASSANDRA?
    • SEARCH + CASSANDRA, 1• First implementation: Solandra (originally Lucandra)• Replaced Lucene index with Cassandra column families
    • SEARCH + CASSANDRA, 2• DataStax Enterprise Search• Uses native Lucene index• All data is retrieved from Cassandra
    • Datastax Enterprise Search ClusterDistributedLinearly ScalableHighly AvailableEventually ConsistentFull-text searchAggregation
    • SETTING UPTHE SCHEMA<fields><field name="id" type="string" indexed="true" stored="true"/><field name="name" type="text" indexed="true" stored="true"/><field name="body" type="text" indexed="true" stored="true"/><field name="title" type="text" indexed="true" stored="true"/><field name="date" type="string" indexed="true" stored="true"/></fields>
    • WRITINGTO CLUSTER• Write to either Cassandra clients or Solr API• Write process is the same• True atomic updates to Cassandra
    • Cassandra nodes are set up according to row-key hash.
    • Data can be written directly to Cassandra
    • Data is distributed according to row key hash and replicationfactor
    • DSE first writes toCassandra
    • And then updates thesecondary index on Solr
    • The quorum responds with success / failure
    • Data is now distributed evenly
    • READING FROM CLUSTER• Read either Cassandra-side or through Solr API• Cassandra: fast reads*• Solr: full-text search• Read direction affects performance• Data is stored in Cassandra
    • Query is sent to node
    • Node uses gossip to find who has the information
    • QUERYING CASSANDRA• Can query Solr or Cassandra directly• Limited syntax with CQL, can use solr_query parameter
    • Querying Cassandradirectly
    • Cassandra retrievesinformation from columnfamily
    • Querying Solr index
    • Row-key hashes arestored in Solr, andCassandra is queried forstored data
    • Cassandra node sendsrequest to node with thecorresponding hash,returns information
    • Data is always synced
    • Both nodes respond with information
    • Updates can be committed and searched over in real time
    • PRODUCTION USE• Will want a mix of analytics, search nodes
    • An OLTP - OLAP integrated solution
    • TRADEOFFS• Changing the Solr schema requires reindex (standard for Solr)• No multi-valued fields or composite columns
    • Q&A@PatriciaGorlapgorla@o19s.como19s.com/blog