@celigo/api-specs 0.2.207 → 0.2.208
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/api.yml +15 -3
- package/dist/connection.yml +15 -3
- package/dist/enduser.yml +15 -3
- package/dist/export.yml +22 -11
- package/dist/flow.yml +19 -10
- package/dist/import.yml +1 -0
- package/dist/mcp-server.yml +15 -3
- package/dist/tool.yml +19 -4
- package/package.json +1 -1
- package/schemas.json +1 -1
package/dist/api.yml
CHANGED
|
@@ -11328,9 +11328,21 @@ components:
|
|
|
11328
11328
|
- COMPUTE_WH
|
|
11329
11329
|
schema:
|
|
11330
11330
|
type: string
|
|
11331
|
-
description:
|
|
11332
|
-
Default
|
|
11333
|
-
|
|
11331
|
+
description: |-
|
|
11332
|
+
Default schema for the session: unqualified table names in queries resolve here, and
|
|
11333
|
+
optimized bulk load imports create their temporary staging table here even when the
|
|
11334
|
+
destination table is schema-qualified — so the connection's role must be able to
|
|
11335
|
+
create that table in it. When blank, optimized bulk load uses PUBLIC.
|
|
11336
|
+
x-celigo-ai-guidance:
|
|
11337
|
+
- |-
|
|
11338
|
+
When this names a schema the session cannot resolve — Snowflake reports it as not
|
|
11339
|
+
existing or not authorized for the role, and the session is left without a current
|
|
11340
|
+
schema — every optimized bulk load fails at the staging step with code `query_fail`
|
|
11341
|
+
and the message "Failed to run the bulk load query. Err: [TempTableQuery] The
|
|
11342
|
+
provided schema is invalid: <this value>" (the connector's rewrite of Snowflake's
|
|
11343
|
+
"This session does not have a current schema"). Fix: set this to a schema the role
|
|
11344
|
+
can create the staging table in — normally the destination table's own schema — or
|
|
11345
|
+
point the import at a second Snowflake connection with that default schema.
|
|
11334
11346
|
examples:
|
|
11335
11347
|
- PUBLIC
|
|
11336
11348
|
role:
|
package/dist/connection.yml
CHANGED
|
@@ -7161,9 +7161,21 @@ components:
|
|
|
7161
7161
|
- COMPUTE_WH
|
|
7162
7162
|
schema:
|
|
7163
7163
|
type: string
|
|
7164
|
-
description:
|
|
7165
|
-
Default
|
|
7166
|
-
|
|
7164
|
+
description: |-
|
|
7165
|
+
Default schema for the session: unqualified table names in queries resolve here, and
|
|
7166
|
+
optimized bulk load imports create their temporary staging table here even when the
|
|
7167
|
+
destination table is schema-qualified — so the connection's role must be able to
|
|
7168
|
+
create that table in it. When blank, optimized bulk load uses PUBLIC.
|
|
7169
|
+
x-celigo-ai-guidance:
|
|
7170
|
+
- |-
|
|
7171
|
+
When this names a schema the session cannot resolve — Snowflake reports it as not
|
|
7172
|
+
existing or not authorized for the role, and the session is left without a current
|
|
7173
|
+
schema — every optimized bulk load fails at the staging step with code `query_fail`
|
|
7174
|
+
and the message "Failed to run the bulk load query. Err: [TempTableQuery] The
|
|
7175
|
+
provided schema is invalid: <this value>" (the connector's rewrite of Snowflake's
|
|
7176
|
+
"This session does not have a current schema"). Fix: set this to a schema the role
|
|
7177
|
+
can create the staging table in — normally the destination table's own schema — or
|
|
7178
|
+
point the import at a second Snowflake connection with that default schema.
|
|
7167
7179
|
examples:
|
|
7168
7180
|
- PUBLIC
|
|
7169
7181
|
role:
|
package/dist/enduser.yml
CHANGED
|
@@ -5186,9 +5186,21 @@ components:
|
|
|
5186
5186
|
- COMPUTE_WH
|
|
5187
5187
|
schema:
|
|
5188
5188
|
type: string
|
|
5189
|
-
description:
|
|
5190
|
-
Default
|
|
5191
|
-
|
|
5189
|
+
description: |-
|
|
5190
|
+
Default schema for the session: unqualified table names in queries resolve here, and
|
|
5191
|
+
optimized bulk load imports create their temporary staging table here even when the
|
|
5192
|
+
destination table is schema-qualified — so the connection's role must be able to
|
|
5193
|
+
create that table in it. When blank, optimized bulk load uses PUBLIC.
|
|
5194
|
+
x-celigo-ai-guidance:
|
|
5195
|
+
- |-
|
|
5196
|
+
When this names a schema the session cannot resolve — Snowflake reports it as not
|
|
5197
|
+
existing or not authorized for the role, and the session is left without a current
|
|
5198
|
+
schema — every optimized bulk load fails at the staging step with code `query_fail`
|
|
5199
|
+
and the message "Failed to run the bulk load query. Err: [TempTableQuery] The
|
|
5200
|
+
provided schema is invalid: <this value>" (the connector's rewrite of Snowflake's
|
|
5201
|
+
"This session does not have a current schema"). Fix: set this to a schema the role
|
|
5202
|
+
can create the staging table in — normally the destination table's own schema — or
|
|
5203
|
+
point the import at a second Snowflake connection with that default schema.
|
|
5192
5204
|
examples:
|
|
5193
5205
|
- PUBLIC
|
|
5194
5206
|
role:
|
package/dist/export.yml
CHANGED
|
@@ -16424,7 +16424,9 @@ components:
|
|
|
16424
16424
|
`POST /v1/exports/preview` reads the `mockOutput` in its request body, not the saved one. For
|
|
16425
16425
|
an export the preview supports (an HTTP export, for example), a body that carries it (as an
|
|
16426
16426
|
export read back with GET does) returns that snapshot as a lone `parse` stage without calling
|
|
16427
|
-
the source; remove `mockOutput` from the body to preview live records.
|
|
16427
|
+
the source; remove `mockOutput` from the body to preview live records. A body mock with an
|
|
16428
|
+
empty or missing `page_of_records` still skips the source and returns 200 with empty `data`
|
|
16429
|
+
and an empty `parse` stage.
|
|
16428
16430
|
|
|
16429
16431
|
**Limitations**
|
|
16430
16432
|
|
|
@@ -17989,17 +17991,27 @@ components:
|
|
|
17989
17991
|
dataURIs:
|
|
17990
17992
|
type: array
|
|
17991
17993
|
description: |-
|
|
17992
|
-
|
|
17993
|
-
|
|
17994
|
+
Links to the records in the source system. On an export preview, one
|
|
17995
|
+
entry per record in `data`: a link to the record when one is available
|
|
17996
|
+
(for example the export's `dataURITemplate` rendered for that record),
|
|
17997
|
+
otherwise `null`, as on an HTTP export without a template; absent when
|
|
17998
|
+
the preview returned no records and when a `mockOutput` in the request
|
|
17999
|
+
body answered.
|
|
17994
18000
|
items:
|
|
17995
|
-
type:
|
|
18001
|
+
type:
|
|
18002
|
+
- string
|
|
18003
|
+
- 'null'
|
|
17996
18004
|
dataRecordTraceKeys:
|
|
17997
18005
|
type: array
|
|
17998
18006
|
description: |-
|
|
17999
18007
|
Trace keys for the records in this preview — one per record,
|
|
18000
|
-
correlating stage outputs to their source record
|
|
18008
|
+
correlating stage outputs to their source record; `null` for a record
|
|
18009
|
+
that has no key. Absent when the preview returned no records and
|
|
18010
|
+
captured no keys, and when a `mockOutput` in the request body answered.
|
|
18001
18011
|
items:
|
|
18002
|
-
type:
|
|
18012
|
+
type:
|
|
18013
|
+
- string
|
|
18014
|
+
- 'null'
|
|
18003
18015
|
stages:
|
|
18004
18016
|
type: array
|
|
18005
18017
|
description: |-
|
|
@@ -18062,12 +18074,11 @@ components:
|
|
|
18062
18074
|
type: object
|
|
18063
18075
|
additionalProperties: true
|
|
18064
18076
|
traceKeysDuplicate:
|
|
18065
|
-
type:
|
|
18077
|
+
type: boolean
|
|
18066
18078
|
description: |-
|
|
18067
|
-
|
|
18068
|
-
|
|
18069
|
-
|
|
18070
|
-
type: string
|
|
18079
|
+
When true, two or more records in this preview share a trace key, so
|
|
18080
|
+
the export's `traceKeyTemplate` does not identify records uniquely.
|
|
18081
|
+
Absent whenever `dataRecordTraceKeys` is absent.
|
|
18071
18082
|
PreviewRequest:
|
|
18072
18083
|
type: object
|
|
18073
18084
|
description: Request body for previewing export data
|
package/dist/flow.yml
CHANGED
|
@@ -8824,17 +8824,27 @@ components:
|
|
|
8824
8824
|
dataURIs:
|
|
8825
8825
|
type: array
|
|
8826
8826
|
description: |-
|
|
8827
|
-
|
|
8828
|
-
|
|
8827
|
+
Links to the records in the source system. On an export preview, one
|
|
8828
|
+
entry per record in `data`: a link to the record when one is available
|
|
8829
|
+
(for example the export's `dataURITemplate` rendered for that record),
|
|
8830
|
+
otherwise `null`, as on an HTTP export without a template; absent when
|
|
8831
|
+
the preview returned no records and when a `mockOutput` in the request
|
|
8832
|
+
body answered.
|
|
8829
8833
|
items:
|
|
8830
|
-
type:
|
|
8834
|
+
type:
|
|
8835
|
+
- string
|
|
8836
|
+
- 'null'
|
|
8831
8837
|
dataRecordTraceKeys:
|
|
8832
8838
|
type: array
|
|
8833
8839
|
description: |-
|
|
8834
8840
|
Trace keys for the records in this preview — one per record,
|
|
8835
|
-
correlating stage outputs to their source record
|
|
8841
|
+
correlating stage outputs to their source record; `null` for a record
|
|
8842
|
+
that has no key. Absent when the preview returned no records and
|
|
8843
|
+
captured no keys, and when a `mockOutput` in the request body answered.
|
|
8836
8844
|
items:
|
|
8837
|
-
type:
|
|
8845
|
+
type:
|
|
8846
|
+
- string
|
|
8847
|
+
- 'null'
|
|
8838
8848
|
stages:
|
|
8839
8849
|
type: array
|
|
8840
8850
|
description: |-
|
|
@@ -8897,12 +8907,11 @@ components:
|
|
|
8897
8907
|
type: object
|
|
8898
8908
|
additionalProperties: true
|
|
8899
8909
|
traceKeysDuplicate:
|
|
8900
|
-
type:
|
|
8910
|
+
type: boolean
|
|
8901
8911
|
description: |-
|
|
8902
|
-
|
|
8903
|
-
|
|
8904
|
-
|
|
8905
|
-
type: string
|
|
8912
|
+
When true, two or more records in this preview share a trace key, so
|
|
8913
|
+
the export's `traceKeyTemplate` does not identify records uniquely.
|
|
8914
|
+
Absent whenever `dataRecordTraceKeys` is absent.
|
|
8906
8915
|
DependencyEntry:
|
|
8907
8916
|
type: object
|
|
8908
8917
|
description: A single resource that depends on the queried resource.
|
package/dist/import.yml
CHANGED
|
@@ -5681,6 +5681,7 @@ components:
|
|
|
5681
5681
|
description: |-
|
|
5682
5682
|
Target table for the bulk load.
|
|
5683
5683
|
Must reference an existing table accessible with the connection's credentials; schema-qualified names are supported.
|
|
5684
|
+
On Snowflake, the temporary staging table that precedes the load is created in the connection's default schema (`rdbms.snowflake.schema` on the connection), not in this table's schema.
|
|
5684
5685
|
x-celigo-ai-guidance:
|
|
5685
5686
|
- |-
|
|
5686
5687
|
The name of the target table within the relational database management system
|
package/dist/mcp-server.yml
CHANGED
|
@@ -8103,9 +8103,21 @@ components:
|
|
|
8103
8103
|
- COMPUTE_WH
|
|
8104
8104
|
schema:
|
|
8105
8105
|
type: string
|
|
8106
|
-
description:
|
|
8107
|
-
Default
|
|
8108
|
-
|
|
8106
|
+
description: |-
|
|
8107
|
+
Default schema for the session: unqualified table names in queries resolve here, and
|
|
8108
|
+
optimized bulk load imports create their temporary staging table here even when the
|
|
8109
|
+
destination table is schema-qualified — so the connection's role must be able to
|
|
8110
|
+
create that table in it. When blank, optimized bulk load uses PUBLIC.
|
|
8111
|
+
x-celigo-ai-guidance:
|
|
8112
|
+
- |-
|
|
8113
|
+
When this names a schema the session cannot resolve — Snowflake reports it as not
|
|
8114
|
+
existing or not authorized for the role, and the session is left without a current
|
|
8115
|
+
schema — every optimized bulk load fails at the staging step with code `query_fail`
|
|
8116
|
+
and the message "Failed to run the bulk load query. Err: [TempTableQuery] The
|
|
8117
|
+
provided schema is invalid: <this value>" (the connector's rewrite of Snowflake's
|
|
8118
|
+
"This session does not have a current schema"). Fix: set this to a schema the role
|
|
8119
|
+
can create the staging table in — normally the destination table's own schema — or
|
|
8120
|
+
point the import at a second Snowflake connection with that default schema.
|
|
8109
8121
|
examples:
|
|
8110
8122
|
- PUBLIC
|
|
8111
8123
|
role:
|
package/dist/tool.yml
CHANGED
|
@@ -10658,9 +10658,21 @@ components:
|
|
|
10658
10658
|
- COMPUTE_WH
|
|
10659
10659
|
schema:
|
|
10660
10660
|
type: string
|
|
10661
|
-
description:
|
|
10662
|
-
Default
|
|
10663
|
-
|
|
10661
|
+
description: |-
|
|
10662
|
+
Default schema for the session: unqualified table names in queries resolve here, and
|
|
10663
|
+
optimized bulk load imports create their temporary staging table here even when the
|
|
10664
|
+
destination table is schema-qualified — so the connection's role must be able to
|
|
10665
|
+
create that table in it. When blank, optimized bulk load uses PUBLIC.
|
|
10666
|
+
x-celigo-ai-guidance:
|
|
10667
|
+
- |-
|
|
10668
|
+
When this names a schema the session cannot resolve — Snowflake reports it as not
|
|
10669
|
+
existing or not authorized for the role, and the session is left without a current
|
|
10670
|
+
schema — every optimized bulk load fails at the staging step with code `query_fail`
|
|
10671
|
+
and the message "Failed to run the bulk load query. Err: [TempTableQuery] The
|
|
10672
|
+
provided schema is invalid: <this value>" (the connector's rewrite of Snowflake's
|
|
10673
|
+
"This session does not have a current schema"). Fix: set this to a schema the role
|
|
10674
|
+
can create the staging table in — normally the destination table's own schema — or
|
|
10675
|
+
point the import at a second Snowflake connection with that default schema.
|
|
10664
10676
|
examples:
|
|
10665
10677
|
- PUBLIC
|
|
10666
10678
|
role:
|
|
@@ -17556,6 +17568,7 @@ components:
|
|
|
17556
17568
|
description: |-
|
|
17557
17569
|
Target table for the bulk load.
|
|
17558
17570
|
Must reference an existing table accessible with the connection's credentials; schema-qualified names are supported.
|
|
17571
|
+
On Snowflake, the temporary staging table that precedes the load is created in the connection's default schema (`rdbms.snowflake.schema` on the connection), not in this table's schema.
|
|
17559
17572
|
x-celigo-ai-guidance:
|
|
17560
17573
|
- |-
|
|
17561
17574
|
The name of the target table within the relational database management system
|
|
@@ -38239,7 +38252,9 @@ components:
|
|
|
38239
38252
|
`POST /v1/exports/preview` reads the `mockOutput` in its request body, not the saved one. For
|
|
38240
38253
|
an export the preview supports (an HTTP export, for example), a body that carries it (as an
|
|
38241
38254
|
export read back with GET does) returns that snapshot as a lone `parse` stage without calling
|
|
38242
|
-
the source; remove `mockOutput` from the body to preview live records.
|
|
38255
|
+
the source; remove `mockOutput` from the body to preview live records. A body mock with an
|
|
38256
|
+
empty or missing `page_of_records` still skips the source and returns 200 with empty `data`
|
|
38257
|
+
and an empty `parse` stage.
|
|
38243
38258
|
|
|
38244
38259
|
**Limitations**
|
|
38245
38260
|
|
package/package.json
CHANGED