[WIP] Doc 81 teradata sql connector#857
Conversation
| </Warning> | ||
|
|
||
| Here is an example table schema that is compatible with Unstructured. It includes all of the required and recommended columns, as | ||
| If you specify a table name and it does not exist, Unstructured creates it with the standard schema. If a table name is not specified or already exists, Unstructured creates a table called `<unstructuredautocreated>`. |
There was a problem hiding this comment.
If a table name already exists, why would Unstructured then create a table called <unstructuredautocreated>? Why wouldn't Unstructured just use the existing table?
There was a problem hiding this comment.
I understood it to mean if there's a table that's different with the same name (not one you created already for this same process) then it would create a new one. Will confirm.
|
|
||
| Here is an example table schema that is compatible with Unstructured. It includes all of the required and recommended columns, as | ||
| If you specify a table name and it does not exist, Unstructured creates it with the standard schema. If a table name is not specified or already exists, Unstructured creates a table called `<unstructuredautocreated>`. | ||
| If you leave the table name blank, you must check the **Metadata as JSON** option in the UI or set `metadata_as_json` to **true** in the API. |
There was a problem hiding this comment.
What happens in this case if you forget to check this option?
There was a problem hiding this comment.
Will ask, I think you get an error?
| PRIMARY INDEX ("id"); | ||
| ``` | ||
|
|
||
| Following is a legacy example table schema that is compatible with Unstructured. It includes all of the required and recommended columns, as |
There was a problem hiding this comment.
When would I want to use this legacy table schema instead of the standard schema?
There was a problem hiding this comment.
I'll check with Potter. He said to leave it in, but you're right, we might need to explain better. Above it says you CAN use the columns if you need them.
| @@ -0,0 +1,7 @@ | |||
| { | |||
There was a problem hiding this comment.
Is this file intended to be checked in to this PR?
There was a problem hiding this comment.
I think it's an artifact that somehow got mixed in, will delete.
andrea-unstructured
left a comment
andrea-unstructured
left a comment
There was a problem hiding this comment.
Addressed questions from Paul.
| PRIMARY INDEX ("id"); | ||
| ``` | ||
|
|
||
| The following legacy example table schema is used if you leave **Metadata as JSON** blank. It includes all of the required and recommended columns, as |
There was a problem hiding this comment.
It it safe to assume that this is also the behavior if you set metadata_as_json to false or don't specify it altogether?
There was a problem hiding this comment.
I made a couple small updates.
2 participants
Updates to the teradata sql connector to include auto-created table name information.