Thanks Ravi, that explains it quite well actually.
Anirudha
On Wed, Apr 1, 2015 at 10:38 AM, Ravi Kiran
wrote:
> Hi Anirudha,
>
>The following link
> https://groups.google.com/forum/#!msg/phoenix-hbase-user/UWdBghSfePo/BmCxOUOPHn8J
> can be helpful.
>
> Regards
> Ravi
>
> On Wed, Apr 1, 201
Hi Anirudha,
The following link
https://groups.google.com/forum/#!msg/phoenix-hbase-user/UWdBghSfePo/BmCxOUOPHn8J
can be helpful.
Regards
Ravi
On Wed, Apr 1, 2015 at 9:55 AM, Anirudha Khanna
wrote:
> Can you explain that a little more please. I dont think I follow.
>
> Anirudha
>
> On Wed,
Can you explain that a little more please. I dont think I follow.
Anirudha
On Wed, Apr 1, 2015 at 12:56 AM, Thomas D'Silva
wrote:
> I think its to support the case when all columns of the table are part
> of primary key (and are used to construct the rowkey).
>
> On Tue, Mar 31, 2015 at 6:23 AM
I think its to support the case when all columns of the table are part
of primary key (and are used to construct the rowkey).
On Tue, Mar 31, 2015 at 6:23 AM, Anirudha Khanna
wrote:
> Hi All,
>
> I am creating updatable views on a Phoenix table and inserting data into the
> table through the view
Hi All,
I am creating updatable views on a Phoenix table and inserting data into
the table through the views. When I inspect the table through the HBase
shell, I see an extra column there
*0:_0timestamp=1427807823285,
value=*
Just curious why is this colum
