Bugfix for Schema Change: Support for Relations and Objects

Open
#237 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
tooling

Research direction

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.

Written by the indexing model from the issue text.

Description

bug

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' />
Dominant language
Python
Stars
363
Forks
183
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from tableau/document-api-python

All issues in tableau/document-api-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.