Bugfix for Schema Change: Support for Relations and Objects
還沒有人認領這個 Issue。
評估
研究方向
No source files or tests are named. Start by locating the schema-change handling and the relation/object XML serialization in the Python library, then reproduce the documented XML variations. Done means schema changes propagate to the connection, both legacy and current relation forms, and nested relation objects.
由索引模型根據 Issue 內容生成。
描述
We are seeing the Documents API 0.10 change the Schema within the connection control (in Tableau Desktop, the grey connection pane and in XML, the connection layer), but we are not seeing this change propagate the relations and object (the "wrapper" for the noodle and the enclosed table in Desktop on the white data canvas or the relation connection and objects within XML (snippet to follow in comment). Without all 4 (1 connection control, 2 relations (true and false) and object) changes, the schema will not deploy.
Connection:
<connection authentication='Username Password' class='redacted' dbname='DB' odbc-connect-string-extras='' one-time-sql='' schema='CHANGE_SCHEMA_HERE' server='redacted' server-oauth='' service='' username='UN' warehouse='WH' workgroup-auth-mode='prompt' />
Relations (for both current and prior version compatibility)
<_.fcp.ObjectModelEncapsulateLegacy.false...relation connection='redacted' name='TABLE' table='[CHANGE_SCHEMA_HERE].[TABLE]' type='table' />
<_.fcp.ObjectModelEncapsulateLegacy.true...relation connection='redacted' name='TABLE' table='[CHANGE_SCHEMA_HERE].[TABLE]' type='table' />
<refresh increment-key='' incremental-updates='false' />
Object
<relation connection='redacted' name='TABLE' table='[CHANGE_SCHEMA_HERE].[TABLE]' type='table' />
Variations
When using a relation, the tags are further nested in the XML under a collection type:
<_.fcp.ObjectModelEncapsulateLegacy.true...relation type='collection'>
<relation connection='redacted' name='TABLE' table='[CHANGE_SCHEMA_HERE].[TABLE]' type='table' />
<relation connection='REDACTED' name='TABLE_2' table='[CHANGE_SCHEMA_HERE].[TABLE_2]' type='table' />
- 主要語言
- Python
- 星號
- 363
- 分支
- 183
- PR 合併指標
- 30 天內沒有已合併 PR
貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
tableau/document-api-python 的其他 Issue
-
難度 5/5 一週以上 新手友好度 20/100
tableau/document-api-python#270 ·
-
難度 4/5 3-5 天 新手友好度 25/100
tableau/document-api-python#260 ·
-
docs
難度 2/5 1-3 小時 新手友好度 55/100
tableau/document-api-python#258 ·
-
難度 5/5 一週以上 新手友好度 30/100
tableau/document-api-python#251 · 2 則留言 ·
-
難度 5/5 一週以上 新手友好度 20/100
tableau/document-api-python#250 · 2 則留言 ·
查看 tableau/document-api-python 的全部 Issue
相似的 Issue
-
essnmx good first issue
難度 1/5 1 小時以內 新手友好度 95/100
-
難度 2/5 1-3 小時 新手友好度 65/100
syfoud/Simulated_Scepter#174 ·
-
難度 2/5 1-3 小時 新手友好度 75/100
Giskard-AI/giskard-oss#2840 · 1 則留言 ·
-
A claim comment carrying the issue number is silently declined while the workflow reports success 未關閉area: repo bug perceived difficulty: 2
難度 2/5 1-3 小時 新手友好度 70/100
-
難度 2/5 1-3 小時 新手友好度 75/100
yeti-platform/yeti#1380 ·