I agree w/ DuyHai regarding the index. The use case described here is a terrible one for SASI indexes.
Regarding MVs, do not use the ones that shipped with 3.x. They're not ready for production. Manage it yourself by using a second table and inserting a second record there. On Thu, Feb 16, 2017 at 7:06 AM DuyHai Doan <doanduy...@gmail.com> wrote: > Using MV and put id as partition key is your best bet right now. SASI will > be too expensive for this simple use case > > On Thu, Feb 16, 2017 at 3:21 PM, Micha <mich...@fantasymail.de> wrote: > > > > it's like having a table (sha256 blob primary key, id timeuuid, data1 > text, ....., ) > > So both, sha256 and id are unique. > I would like to query *either* with sha256 *or* with id. > > I thought this can be done with a sasi index, but it has to be done with > a second table (manual way) or with a mv with id as partition key. > > On 16.02.2017 15:11, Benjamin Roth wrote: > > No matter what has to be indexed here, the preferrable way is most > > probably denormalization instead of another index. > > it's rather manual inserting the data with another partition key or make > a mv for with the other key. > > >
