Skip to main content

Posts

Showing posts with the label index

Introduction to Couchbase for Oracle Developers & Experts: Part 6: indexing

"Use the Index, Luke!"  --  https://use-the-index-luke.com ORACLE Couchbase OVERVIEW Index Documentation Index Documentation Types of Indexes:  Primary & secondary Index (B-tree) Bitmap Index Partial Index Partitioned Index Function-based index Spatial index Search indexes (full text search) Types of Indexes:  Primary & secondary index (lock-free skiplist) Partial index Partitioned index Functional-key index Array index Flex indexes Search index Spatial index Indexing data structures B-Tree Bitmap Spatial Inverted tree Indexing data structures Lock-free skiplist Inverted tree (text) Z-curve (spatial) CLASSES of INDEXES Oracle indexes which can be large and is managed thru bufferpools.  Oracle text index can be creed with inmemory option. Couchbase has two classes of indexes: Standard secondary index which can be large and relevant entries are paged in based on usage, memory optimized index , optimized for performance is entirely kept in memory and a wri...

Flexible Query and Indexing for Flexible JSON Model

  Use N1QL when you're in a JSON pickle. - Confucius For the JSON data model, the general advice is to think of collections as tables, JSON documents as denormalized rows, and field names as columns — roughly. All this holds true in databases like Couchbase and MongoDB when recommendations are strictly followed. There are many reasons why users don't simply follow this key-value pair model  all the time.  Here are the main reasons: You want to convert a map/hashmap data structure where the keys are dynamic. Timeseries data when the field names are usually encoded timestamps. Dictionary based encoding . Existing document formats and standards disallow redesign. If your database and query language the query language doesn't deal with the situation, you've to go through an elaborate redesign. In addition to simply accessing the information, how do you make the queries on JSON efficient when you don't even know the name of the field you have to index on? Fortunately, Co...