Merge branch 'master' into ft.info-complexity

Ariel Shtul · web-flow · commit 0d9bee74c402 · 2021-08-02T12:42:06.000+03:00
diff --git a/docs/Commands.md b/docs/Commands.md
@@ -230,6 +230,9 @@ FT.CREATE idx ON JSON SCHEMA $.title AS title TEXT $.categories AS categories TA
         must be a single character.
 
     * **CASESENSITIVE**
+        
+        For `TAG` attributes, keeps the original letter cases of the tags.
+        If not specified, the characters are converted to lowercase.
 
 #### Complexity
 O(1)
diff --git a/docs/Tags.md b/docs/Tags.md
@@ -1,29 +1,33 @@
 # Tag Fields
 
-RediSearch 0.91 adds a new kind of field - the Tag field. They are similar to full-text fields but use simpler tokenization and encoding in the index. The values in these fields cannot be accessed by general field-less search and can be used only with a special syntax.
+Tag fields are similar to full-text fields but use simpler tokenization and encoding in the index. The values in these fields cannot be accessed by general field-less search and can be used only with a special syntax.
 
 The main differences between tag and full-text fields are:
 
 1. We do not perform stemming on tag indexes.
 
-2. The tokenization is simpler: The user can determine a separator (defaults to a comma) for multiple tags, and we only do whitespace trimming at the end of tags. Thus, tags can contain spaces, punctuation marks, accents, etc. The only two transformations we perform are lower-casing (for latin languages only as of now), and whitespace trimming.
+2. The tokenization is simpler: The user can determine a separator (defaults to a comma) for multiple tags, and we only do whitespace trimming at the end of tags. Thus, tags can contain spaces, punctuation marks, accents, etc.
 
-3. Tags cannot be found from a general full-text search. If a document has a field called "tags" with the values "foo" and "bar", searching for foo or bar without a special tag modifier (see below) will not return this document.
+3. The only two transformations we perform are lower-casing (for latin languages only as of now) and whitespace trimming. Lower-case transformation can be disabled by passing CASESENSITIVE.
 
-4. The index is much simpler and more compressed: We do not store frequencies, offset vectors of field flags. The index contains only document IDs encoded as deltas. This means that an entry in a tag index is usually one or two bytes long. This makes them very memory efficient and fast.
+4. Tags cannot be found from a general full-text search. If a document has a field called "tags" with the values "foo" and "bar", searching for foo or bar without a special tag modifier (see below) will not return this document.
 
-5. An unlimited number of tag fields can be created per index, as long as the overall number of fields is under 1024.
+5. The index is much simpler and more compressed: We do not store frequencies, offset vectors of field flags. The index contains only document IDs encoded as deltas. This means that an entry in a tag index is usually one or two bytes long. This makes them very memory efficient and fast.
+
+6. An unlimited number of tag fields can be created per index, as long as the overall number of fields is under 1024.
 
 ## Creating a tag field
 
 Tag fields can be added to the schema in FT.ADD with the following syntax:
 
 ```
-FT.CREATE ... SCHEMA ... {field_name} TAG [SEPARATOR {sep}]
+FT.CREATE ... SCHEMA ... {field_name} TAG [SEPARATOR {sep}] [CASESENSITIVE]
 ```
 
 SEPARATOR defaults to a comma (`,`), and can be any printable ASCII character. For example:
 
+CASESENSITIVE can be specified to keep the original letters case.
+
 ```
 FT.CREATE idx ON HASH PREFIX 1 test: SCHEMA tags TAG SEPARATOR ";"
 ```
