besides the name, so you can specify only the fields you want to change. All the names correspond to the snake/lowercase versions of the arguments you would use on the command line with redis-cli or in redis-py. For more on the arguments for each field, see the documentationThe below example shows how to specify the schema for the credit_score field as a Tag (categorical) field instead of a text field. # index_schema.ymltag:    - name: credit_scoretext:    - name: user    - name: jobnumeric:    - name: ageIn Python this would look like:index_schema = {    "tag": [{"name": "credit_score"}],    "text": [{"name": "user"}, {"name": "job"}],    "numeric": [{"name": "age"}],}Notice that only the name field needs to be specified. All other fields have defaults.# create a new index with the new schema defined aboveindex_schema = {    "tag": [{"name": "credit_score"}],    "text": [{"name": "user"}, {"name": "job"}],    "numeric": [{"name": "age"}],}rds, keys = Redis.from_texts_return_keys(    texts,    embeddings,    metadatas=metadata,    redis_url="redis://localhost:6379",    index_name="users_modified",    index_schema=index_schema, # pass in the new index schema)    `index_schema` does not match generated metadata schema.    If you meant to manually override the schema, please ignore this message.    index_schema: {'tag': [{'name': 'credit_score'}], 'text': [{'name': 'user'}, {'name': 'job'}], 'numeric': [{'name': 'age'}]}    generated_schema: {'text': [{'name': 'user'}, {'name': 'job'}, {'name': 'credit_score'}], 'numeric': [{'name': 'age'}], 'tag': []}    The above warning is meant to notify users when they are overriding the default behavior. Ignore it if you are intentionally overriding the behavior.Hybrid Filteringâ€‹With the Redis Filter Expression language built into langchain, you can create arbitrarily long chains of hybrid filters
Redis vector database introduction and langchain integration guide.
Redis vector database introduction and langchain integration guide. ->: besides the name, so you can specify only the fields you want to change. All the names correspond to the snake/lowercase versions of the arguments you would use on the command line with redis-cli or in redis-py. For more on the arguments for each field, see the documentationThe below example shows how to specify the schema for the credit_score field as a Tag (categorical) field instead of a text field. # index_schema.ymltag:    - name: credit_scoretext:    - name: user    - name: jobnumeric:    - name: ageIn Python this would look like:index_schema = {    "tag": [{"name": "credit_score"}],    "text": [{"name": "user"}, {"name": "job"}],    "numeric": [{"name": "age"}],}Notice that only the name field needs to be specified. All other fields have defaults.# create a new index with the new schema defined aboveindex_schema = {    "tag": [{"name": "credit_score"}],    "text": [{"name": "user"}, {"name": "job"}],    "numeric": [{"name": "age"}],}rds, keys = Redis.from_texts_return_keys(    texts,    embeddings,    metadatas=metadata,    redis_url="redis://localhost:6379",    index_name="users_modified",    index_schema=index_schema, # pass in the new index schema)    `index_schema` does not match generated metadata schema.    If you meant to manually override the schema, please ignore this message.    index_schema: {'tag': [{'name': 'credit_score'}], 'text': [{'name': 'user'}, {'name': 'job'}], 'numeric': [{'name': 'age'}]}    generated_schema: {'text': [{'name': 'user'}, {'name': 'job'}, {'name': 'credit_score'}], 'numeric': [{'name': 'age'}], 'tag': []}    The above warning is meant to notify users when they are overriding the default behavior. Ignore it if you are intentionally overriding the behavior.Hybrid Filteringâ€‹With the Redis Filter Expression language built into langchain, you can create arbitrarily long chains of hybrid filters