Your understanding is incorrect. You can update existing rows :)
Would encourage you to read through the HBase book that Stack had
earlier sent. It covers simple architecture questions like this.
http://hbase.apache.org/book.html
Denise Rogers wrote:
In reading the material in the link you sent. It seems that you can update an
existing row through the put command.
I was of the understanding that hbase does not support updates to existing rows.
I just need a definitive rule on updates in hbase.
Regards,
Denise
Sent from mi iPhone
On Nov 11, 2016, at 1:54 PM, Stack<[email protected]> wrote:
Link to 1.1. docs is not up. See under 'Documentation and API' tab. See the
tail of the menu. Just above the 0.94 item, there is a new 1.1 doc.
St.Ack
On Mon, Nov 7, 2016 at 4:30 PM, Stack<[email protected]> wrote:
On Mon, Nov 7, 2016 at 2:43 PM, Sean Busbey<[email protected]> wrote:
I think most folks are looking for javadocs, which vary considerably
across minor release lines.
Sorry. Yes. Indeed that is what Rajeshkumar asked originally.
As penance for my derail of the thread, let me work on putting up a link
to 1.1. doc. this evening.
Thanks,
St.Ack
On Mon, Nov 7, 2016 at 3:10 PM, Stack<[email protected]> wrote:
On Sun, Nov 6, 2016 at 9:23 PM, Yu Li<[email protected]> wrote:
We do have an hbase book for 0.94 specially:
http://hbase.apache.org/0.94/book.html, and it might be a good
question
that shall we supply similar website of different branches for user or
always require them to generate the site by themselves? Current hbase
book
(
http://hbase.apache.org/book.html) contains some new features only
for 2.0
(plz correct me if I'm wrong) so might not be proper for all users to
refer
to?
btw, if plan to use branch-1.1 release, I'd suggest to use versions
later
than (including) 1.1.4 because of HBASE-14460 (
https://issues.apache.org/jira/browse/HBASE-14460, which fixes
performance
regression), JFYI @Rajeshkumar
Best Regards,
Yu
This is a perennial (... that we should publish per-version doc.)
Truth be told, we don't do the work to maintain version specific
documentation. RMs usually copy the current state of the master doc into
their branch before cutting an RC so they get the 'latest' changes. Doc
is
done up on the master branch. Doc will have callouts if a
version-specific
config or feature but we are probably erratic in our practice here (and
in
the converse, deprecating the old and no longer supported).
Doc seems to change at a slow rate so maybe its not so bad that this is
the
case.
That said, if the 1.1 doc has big differences from the master doc., we
could do the same was we did for 0.94 -- making a subdir for 1.1.
St.Ack
On 7 November 2016 at 13:06, Ted Yu<[email protected]> wrote:
I actually run the (modified) command in your first email quite
often -
when building tar balls for cluster testing.
In that case, site goal is not used.
Cheers
On Sun, Nov 6, 2016 at 8:44 PM, Josh Elser<[email protected]>
wrote:
In hindsight, you're probably right, Ted. I was just copying from
the
book
and forgot to remove that execution :)
Ted Yu wrote:
If I am not mistaken, the 'assembly:single' goal is not needed for
building
the site.
Cheers
On Sun, Nov 6, 2016 at 12:57 PM, Josh Elser<[email protected]>
wrote:
Hi,
I don't believe all versions of Javadoc are published on the
website.
Something similar to the following should build it for you
locally.
1. git checkout rel/1.1.1
2. `mvn clean install -DskipTests javadoc:aggregate site
assembly:single`
Rajeshkumar J wrote:
Hi,
We are moving from hbase 0.94 to hbase 1.1.1. Some methods of
hbase
0.94
are deprecated for hbase 1.1.1. So can anyone post me the link
for
Api
documentation for Hbase version 1.1.1 as I can't find that.
Thanks
--
busbey
