[BEAM-9989] Python Schemas: error encoding from generated user types with an "id" field

• Type: Bug
• Status: Resolved
• Priority: P2
• Resolution: Fixed
• Fix Version/s: 2.22.0
• Component/s: sdk-py-core
• Assignee: Brian Hulette
• Reporter: Brian Hulette
• Created: 13/May/20 21:56
• Updated: 29/May/20 17:51
• Resolved: 29/May/20 17:51

Description

This reveals a couple of issues:

• We probably shouldn't store the schema id in an "id" attribute on the type
• We should just treat the named tuple instance as a tuple when reading rather than calling getattr for each schema field

Issue Links

• links to: GitHub Pull Request #11701