Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Moved tests for CLI table #2830

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
+431 −1
Open

Moved tests for CLI table #2830

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions deps.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,3 +7,4 @@ tzdata 1.0.1 240904 3ba592a
! Do not change the separator that splits this desc from the data
This file should contain one line per package with a version lock.
You can find proper values for each dep on https://repo.manticoresearch.com
ou can find proper values for each dep on https://repo.manticoresearch.com
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
ou can find proper values for each dep on https://repo.manticoresearch.com
You can find proper values for each dep on https://repo.manticoresearch.com

2 changes: 2 additions & 0 deletions manual/Creating_a_table/Data_types.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1933,6 +1933,8 @@ Float vector attributes can be used in k-nearest neighbor searches; see [KNN sea

** Currently, `float_vector` fields can only be utilized in KNN search within real-time tables and the data type is not supported in any other functions or expressions, nor is it supported in plain tables. **

** Keep in mind that the `float_vector` data type is not compatible with the [Auto schema](../Data_creation_and_modification/Adding_documents_to_a_table/Adding_documents_to_a_real-time_table.md#Auto-schema) mechanism. **

<!-- intro -->
##### SQL:
<!-- request SQL -->
Expand Down
4 changes: 3 additions & 1 deletion ...dification/Adding_documents_to_a_table/Adding_documents_to_a_real-time_table.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,7 +71,7 @@ POST /insert
{
"table":"products",
"id":0,
"doc":
"doc":
{
"title" : "Yellow bag"
}
Expand Down Expand Up @@ -269,6 +269,8 @@ If you attempt to INSERT multiple rows with different, incompatible value types
* uint -> bigint -> float (this may cause some precision loss)
* string -> text

The auto schema mechanism does not support creating [KNN](../../Searching/KNN.md#Configuring-a-table-for-KNN-search) tables, so you cannot insert `float_vector` data into an automatically created table. If you still want to store `float_vector` values in a regular table, you can insert them using the same syntax as for JSON data.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds a little vague:

  • what is "KNN tables"?
  • "you cannot insert float_vector data into an automatically created table" - it's better to say you can't create a table with fields of type float_vector
  • "If you still want to store float_vector values in a regular table". What's meant by "float_vector" values?
  • "you can insert them using the same syntax as for JSON data" - what's the syntax for JSON data?


Also, the following formats of dates will be recognized and converted to timestamps while all other date formats will be treated as strings:
- `%Y-%m-%dT%H:%M:%E*S%Z`
- `%Y-%m-%d'T'%H:%M:%S%Z`
Expand Down
Loading
Loading