<commit_before>/**
 * <p> Secondary Indexing (2i) in Riak gives developers the ability, at write
 * time, to tag an object stored in Riak with one or more queryable values.
 * 
 * <h4>Introduction</h4>
 * Since the KV data in Riak is completely opaque to 2i, the user must tell 2i exactly
 * what attribute to index on and what its index value should be via key/value
 * metadata. This is different from Search, which parses the data and builds
 * indexes based on a schema. 
 * <p>
 * The classes in this package provide an API for managing secondary indexes. 
 * </p>
 * <p><b>Important note:</b> 2i currently requires Riak to be configured to 
 * use the eleveldb or memory backend. The default bitcask backend does not support
 * 2i.
 * </p> 
 * <h4>Overview</h4>
 * In Riak there are two types of secondary indexes; "integer" and "binary". 
 * The former represents an index with numeric values whereas the second is used
 * for textual (String) data. The server API distinguishes between the two via <commit_msg>One last change to Javadoc. Honest.<commit_after>/**
 * Low-level API for managing Riak Secondary Indexes (2i)
 * 
 * <h4>Introduction</h4>
 * Secondary Indexing (2i) in Riak gives developers the ability, at write
 * time, to tag an object stored in Riak with one or more queryable values.
 * <p>
 * Since the KV data in Riak is completely opaque to 2i, the user must tell 2i exactly
 * what attribute to index on and what its index value should be via key/value
 * metadata. This is different from Search, which parses the data and builds
 * indexes based on a schema. 
 * </p>
 * <p>
 * The classes in this package provide an API for managing secondary indexes. 
 * </p>
 * <p><b>Important note:</b> 2i currently requires Riak to be configured to 
 * use the eleveldb or memory backend. The default bitcask backend does not support
 * 2i.
 * </p> 
 * <h4>Overview</h4>
 * In Riak there are two types of secondary indexes; "integer" and "binary". 
 * The former represents an index with numeric values whereas the second is used
 * for textual (String) data. The server API distinguishes between the two via 
{'fraction_non_alphanumeric': 0.07569346497414198, 'fraction_numerical': 0.008932769158439116, 'mean_word_length': 3.739420935412027, 'pattern_counts': {'":': 0, '<': 26, '<?xml version=': 0, '>': 26, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5044737', 'n_tokens_mistral': 630, 'n_tokens_neox': 578, 'n_words': 320}