[
https://issues.apache.org/jira/browse/HBASE-8165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-8165:
-------------------------
Attachment: 8615v9.txt
One line difference from v8 to fix the javadoc warning. What I committed.
This v9 went into 0.95 but for this reject:
patching file
hbase-protocol/src/main/java/org/apache/hadoop/hbase/protobuf/generated/AuthenticationProtos.java
patching file
hbase-protocol/src/main/java/org/apache/hadoop/hbase/protobuf/generated/CellProtos.java
15 ***************
14 *** 868,874 ****
0 ***************
1 *** 868,874 ****
2 <buildDate>${maven.build.timestamp}</buildDate>
3 <compileSource>1.6</compileSource>
4 <!-- Dependencies -->
5 - <hadoop-two.version>2.0.5-alpha</hadoop-two.version>
6 <hadoop-one.version>1.2.1</hadoop-one.version>
7 <commons-cli.version>1.2</commons-cli.version>
8 <commons-codec.version>1.7</commons-codec.version>
9 --- 872,878 ----
10 <buildDate>${maven.build.timestamp}</buildDate>
11 <compileSource>1.6</compileSource>
12 <!-- Dependencies -->
13 + <hadoop-two.version>2.1.0-beta</hadoop-two.version>
14 <hadoop-one.version>1.2.1</hadoop-one.version>
15 <commons-cli.version>1.2</commons-cli.version>
16 <commons-codec.version>1.7</commons-codec.version>
Rather than post a new 9M patch for 0.95, I just fixed the above before commit.
> Move to Hadoop 2.1.0-beta from 2.0.x-alpha (WAS: Update our protobuf to 2.5
> from 2.4.1)
> ---------------------------------------------------------------------------------------
>
> Key: HBASE-8165
> URL: https://issues.apache.org/jira/browse/HBASE-8165
> Project: HBase
> Issue Type: Bug
> Reporter: stack
> Assignee: stack
> Fix For: 0.98.0, 0.96.0
>
> Attachments: 8165_minus_generated.txt, 8165_trunk7.txt,
> 8165_trunkv6.txt, 8165.txt, 8165v2.txt, 8165v3.txt, 8165v4.txt, 8165v5.txt,
> 8165v8.txt, 8615v9.txt, HBASE-8165-rebased.patch
>
>
> Update to new 2.5 pb. Some speedups and a new PARSER idiom that bypasses
> making a builder.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
