[ https://issues.apache.org/jira/browse/KUDU-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Lipcon resolved KUDU-99. ----------------------------- Resolution: Won't Fix Fix Version/s: n/a Resolving this as wont fix, since the surgery required at this point would be pretty heavy and probably break wire compat. We can re-open if it becomes more urgent such that it's worth the compatibility issues. > Separate internal (e.g., storage related) column attributes from external > ones and change APIs > ---------------------------------------------------------------------------------------------- > > Key: KUDU-99 > URL: https://issues.apache.org/jira/browse/KUDU-99 > Project: Kudu > Issue Type: New Feature > Components: client, master, tablet > Affects Versions: Backlog > Reporter: Alex Feinberg > Fix For: n/a > > > We currently use ColumnSchema (and it's matching protobuf messages > ColumnSchemaPB) to specify both logical (e.g., which data type, what > constitutes a key, is it nullable) and physical (e.g., compression codec, > encoding algorithm) attributes. > We need an approach that allows the user to specify and alter these externals > attributes via our "DDL" APIs, without having to include them in every single > message and data structure: e.g., when sending other data over the wire > (which may as well be encoded in a different format or sent plain text). -- This message was sent by Atlassian JIRA (v6.3.4#6332)