feat: remove match_all_raw

Author: hengfeiyang

docs/example-queries.md

@@ -7,7 +7,7 @@ We will use the k8s [sample logs data](https://zinc-public-data.s3.us-west-2.ama
 - To search for all the fields containing the word `error` using `Inverted Index`:
     - `match_all('error')`
     - - match_all searches only the fields that are configured for full text search. Default set of fields are `log`, `message`, `msg`, `content`, `data`, `json`. If you want more fields to be scanned during full text search, you can configure them under stream settings. You should use `str_match` for full text search in specific fields.
-- Search only `log` field for error. This is much more efficient than `match_all_raw` as it search in a single field.
+- Search only `log` field for error. This is much more efficient than `match_all` as it search in a single field.
     - `str_match(log, 'error')`
 - To search for all log entries that have log entries where `code is 200` . code is a numeric field
     - `code=200`

docs/sql_reference.md

@@ -17,15 +17,7 @@ then you can specify Index Type for one or multiple fields (e.g. `body`, `messag
 
 > We have default fields: `log`, `message`, `msg`, `content`, `data`, `json`. you can set the full text search fields in the UI or through `index.setting` API.
 
-_Please note: `match_all` searches through the inverted indexed terms, which are all indexed in lowercase internally. Therefore, search keywords for `match_all` are case-insensitive. For case-sensitive searches, please use `match_all_raw` and `match_all_raw_ignore_case` described below accordingly._
-
-### match_all_raw('v')
-
-filter the keyword in multiple fields. Unlike `match_all`, `match_all_raw` does not utilize `Inverted Index`, instead searches through entire original data. This function is case-sensitive.
-
-### match_all_raw_ignore_case('v')
-
-same as `match_all_raw` but with case-insensitive.
+_Please note: `match_all` searches through the inverted indexed terms, which are all indexed in lowercase internally. Therefore, search keywords for `match_all` are case-insensitive._
 
 ### re_match(field, 'pattern')
 

docs/user-guide/concepts.md

@@ -51,8 +51,6 @@ For input data with key as `_timestamp`/`@timestamp`, for the value we support t
 
 ### Full text search
 
-For full text search user can use query in-built query functions like `match_all_raw`, `match_all_raw_ignore_case`, please note user can restrict full text search to specific fields/columns in log stream by selecting fields/columns from stream in stream details screen.
+For full text search user can use query in-built query functions `match_all`, please note user can restrict full text search to specific fields/columns in log stream by selecting fields/columns from stream in stream details screen.
 
-### Inverted index search
-
-Similar to full text search, user can enabled inverted index feature and select appropriate fields to be indexed during ingestion. For such fields, user can query function `match_all` for case-insensitive search for all the fields that have Inverted Index set as the `Full text search`.
+If user enabled `Inverted Index`, this function will auto use `Inverted Index` for `Full text search`.

docs/user-guide/functions/index.md

@@ -4,7 +4,7 @@
 
 Functions in OpenObserve are defined using Vector Remap Language ([VRL](https://vrl.dev)) and can be used during ingestion or query to aid advanced capabilities like enrichment, redaction, log reduction, compliance, etc. 
 
-There are also inbuilt query functions like `match_all`, `match_all_raw` and `match_all_raw_ignore_case` etc which can be used for full text search based on user's settings for stream or default settings. Please refer [SQL functions reference](../../sql_reference.md) for complete list of inbuilt functions.
+There are also inbuilt query functions like `match_all` etc which can be used for full text search based on user's settings for stream or default settings. Please refer [SQL functions reference](../../sql_reference.md) for complete list of inbuilt functions.
 
 To navigate to functions in OpenObserve, select preferred organization using organization selection control, then click on `Pipelines > Functions` menu, which will take you to functions list screen. This screen lists all the functions for selected organization.  
 

docs/user-guide/logs/log-search.md

@@ -17,7 +17,7 @@ Logs screen details :
 
 1. Controls to toggle visibility or query mode for search,query, fields & histogram control toggle visibility of Query editor(3) , Fields(6) & Histogram(5) respectively. SQL mode toggle query mode to intellisense mode or full sql mode , based on SQL mode Syntax guide is shown to user.
 1. Controls for absolute & relative date-time selection , refresh options for screen & initiating search
-1. Query editor , the behavior which is affected by sql mode , one can use inbuilt functions like `match_all`, `match_all_raw` and `match_all_raw_ignore_case` or can write complete sql for search
+1. Query editor , the behavior which is affected by sql mode , one can use inbuilt functions like `match_all` or can write complete sql for search
 1. Name of stream belonging to organization which will be target for search , one can change the target stream by selecting one from list
 1. Histogram depicting details like how many records are being shown out of total number of records & total scanned volume(size in mb) eligible for search criteria provided
 1. List of all fields belonging to stream , one can choose to add the field to add to query(3) or to search results table(7)

docs/user-guide/streams.md

@@ -31,5 +31,5 @@ Streams details screen:
 1. Start & end time for steam, these are based timestamps on log records in stream
 1. Name of property/field belonging to the stream
 1. Inferred type of the property, openobserve infers schema for data being ingested
-1. Checkbox to select/deselect a property of the stream as full text search keys, full text search keys are used to search a term when using `match_all`, `match_all_raw`, `match_all_raw_ignore_case`
+1. Checkbox to select/deselect a property of the stream as full text search keys, full text search keys are used to search a term when using `match_all`
 1. Checkbox to select/deselect a property of the stream as partitioning key, data ingested after updating the setting will be partitioned using updated keys