of the ‘views’ are written and some aren’t.
> >
> >
> >
> >
> >
> > From: Pedro Boado [mailto:pedro.bo...@gmail.com]
> > Sent: Friday, September 27, 2019 7:22 AM
> > To: user@phoenix.apache.org
> > Subject: Re: Materialized views in Hbas
Pedro Boado [mailto:pedro.bo...@gmail.com]
> Sent: Friday, September 27, 2019 7:22 AM
> To: user@phoenix.apache.org
> Subject: Re: Materialized views in Hbase/Phoenix
>
>
>
> CAUTION: This email originated from outside the Allen Institute. Please do not
> click links
ich is why I was considering a transaction. We cannot be in
a partial state where some of the ‘views’ are written and some aren’t.
*From:*Pedro Boado [mailto:pedro.bo...@gmail.com]
*Sent:* Friday, September 27, 2019 7:22 AM
*To:* user@phoenix.apache.org
*Subject:* Re: Materialized views in Hba
ta consistency between the tables created for each matrix.
>
>
>
> *From:* Pedro Boado [mailto:pedro.bo...@gmail.com]
> *Sent:* Friday, September 27, 2019 10:53 AM
> *To:* user@phoenix.apache.org
> *Subject:* Re: Materialized views in Hbase/Phoenix
>
>
>
> *CAUTION:* T
created for each matrix.
From: Pedro Boado [mailto:pedro.bo...@gmail.com]
Sent: Friday, September 27, 2019 10:53 AM
To: user@phoenix.apache.org
Subject: Re: Materialized views in Hbase/Phoenix
CAUTION: This email originated from outside the Allen Institute. Please do not
click links or open
column when all rows are grouped by a certain row
> property).
>
>
>
> Precomputing seems much more efficient.
>
>
>
> *From:* Pedro Boado [mailto:pedro.bo...@gmail.com]
> *Sent:* Friday, September 27, 2019 9:27 AM
> *To:* user@phoenix.apache.org
> *Subject:*
.
From: Pedro Boado [mailto:pedro.bo...@gmail.com]
Sent: Friday, September 27, 2019 9:27 AM
To: user@phoenix.apache.org
Subject: Re: Materialized views in Hbase/Phoenix
CAUTION: This email originated from outside the Allen Institute. Please do not
click links or open attachments unless you've
> *From:* Pedro Boado [mailto:pedro.bo...@gmail.com]
> *Sent:* Friday, September 27, 2019 7:22 AM
> *To:* user@phoenix.apache.org
> *Subject:* Re: Materialized views in Hbase/Phoenix
>
>
>
> *CAUTION:* This email originated from outside the Allen Institute. Please
> do not
state
where some of the ‘views’ are written and some aren’t.
From: Pedro Boado [mailto:pedro.bo...@gmail.com]
Sent: Friday, September 27, 2019 7:22 AM
To: user@phoenix.apache.org
Subject: Re: Materialized views in Hbase/Phoenix
CAUTION: This email originated from outside the Allen Institute
e?
>
>
>
> --gautham
>
>
>
>
>
> *From:* anil gupta [mailto:anilgupt...@gmail.com]
> *Sent:* Friday, September 27, 2019 6:58 AM
> *To:* user@phoenix.apache.org
> *Subject:* Re: Materialized views in Hbase/Phoenix
>
>
>
> *CAUTION:* This email ori
[mailto:anilgupt...@gmail.com]
Sent: Friday, September 27, 2019 6:58 AM
To: user@phoenix.apache.org
Subject: Re: Materialized views in Hbase/Phoenix
CAUTION: This email originated from outside the Allen Institute. Please do not
click links or open attachments unless you've validated the sender and know
For your use case, i would suggest to create another table that stores the
matrix. Since this data doesnt change that often, maybe you can write a
nightly spark/MR job to update/rebuild the matrix table.(If you want near
real time that is also possible with any streaming system) Have you looked
12 matches
Mail list logo
