[ https://issues.apache.org/jira/browse/CASSANDRA-19492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Caleb Rackliffe updated CASSANDRA-19492: ---------------------------------------- Change Category: Semantic Complexity: Normal Component/s: Feature/SAI Fix Version/s: 5.0.x 5.x Status: Open (was: Triage Needed) > Allow configurable v4/v6 address matching behavior for SAI indexes on CQL > inet columns > -------------------------------------------------------------------------------------- > > Key: CASSANDRA-19492 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19492 > Project: Cassandra > Issue Type: Improvement > Components: Feature/SAI > Reporter: Caleb Rackliffe > Priority: Normal > Fix For: 5.0.x, 5.x > > > The {{inet}} type in CQL allows ipv4 and ipv6 address formats to mix in the > same column, and while there is a standard conversion between v4 and v6, > equivalent addresses are not considered equal by Cassandra, when it comes to > their usage in keys or in filtering queries. However, in SAI queries, > equivalent v4 and v6 addresses ARE considered equal. Even if this behavior is > useful, it might be a good idea to make the default behavior consistent with > filtering, and allow the index configuration to control whether or not to > consider them equal. (We have precedent for this w/ case-insensitive indexing > of text columns, etc.) -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org