[
https://issues.apache.org/jira/browse/CASSANDRA-14468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16553675#comment-16553675
]
Jordan West edited comment on CASSANDRA-14468 at 7/24/18 1:40 AM:
------------------------------------------------------------------
[~wadey], sorry for taking so long to get to this but I finally had some time
today. I agree with your assessment so far but unfortunately don’t have much to
add. It looks like CASSANDRA-12516 fixed what the cache was keyed on but not
all the {{getInterned}} call sites. Indeed the {{type}} column is the CQL
(value) type. Further, we no longer have the comparator after
{{LegacySchemaMigrator}} runs (of note, {{LegacySchemaMigrator}} does use
{{getInterned}} as intended but since we lose the comparator that only makes
things worse)*.
[~iamaleksey], do you have any thoughts on this since you reported the original
issue?
\* I’m actually just getting familiar with this code but I think [~jasobrown]
referred this ticket to me because of the initial relation to 2i
was (Author: jrwest):
[~wadey], sorry for taking so long to get to this but I finally had some time
today. I agree with your assessment so far but unfortunately don’t have much to
add. It looks like CASSANDRA-12516 fixed what the cache was keyed on but not
all the {{getInterned}} call sites. Indeed the {{type}} column is the CQL
(value) type. Further, we no longer have the comparator after
{{LegacySchemaMigrator}} runs (of note, {{LegacySchemaMigrator}} does use
{{getInterned}} as intended but since we lose the comparator that only makes
things worse)*.
[~iamaleksey], do you have any thoughts on this since you reported the original
issue?
* I’m actually just getting familiar with this code but I think [~jasobrown]
referred this ticket to me because of the initial relation to 2i
> "Unable to parse targets for index" on upgrade to Cassandra 3.0.10-3.0.16
> -------------------------------------------------------------------------
>
> Key: CASSANDRA-14468
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14468
> Project: Cassandra
> Issue Type: Bug
> Reporter: Wade Simmons
> Priority: Major
> Attachments: data.tar.gz
>
>
> I am attempting to upgrade from Cassandra 2.2.10 to 3.0.16. I am getting this
> error:
> {code}
> org.apache.cassandra.exceptions.ConfigurationException: Unable to parse
> targets for index idx_foo ("666f6f")
> at
> org.apache.cassandra.index.internal.CassandraIndex.parseTarget(CassandraIndex.java:800)
> ~[apache-cassandra-3.0.16.jar:3.0.16]
> at
> org.apache.cassandra.index.internal.CassandraIndex.indexCfsMetadata(CassandraIndex.java:747)
> ~[apache-cassandra-3.0.16.jar:3.0.16]
> at
> org.apache.cassandra.db.ColumnFamilyStore.scrubDataDirectories(ColumnFamilyStore.java:645)
> ~[apache-cassandra-3.0.16.jar:3.0.16]
> at
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:251)
> [apache-cassandra-3.0.16.jar:3.0.16]
> at
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:569)
> [apache-cassandra-3.0.16.jar:3.0.16]
> at
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:697)
> [apache-cassandra-3.0.16.jar:3.0.16]
> {code}
> It looks like this might be related to CASSANDRA-14104 that was just added to
> 3.0.16
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
