Hi All
I am trying to create the tar ball from the latest master.
I am getting this error
ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.4:single (default-cli) on
project hbase-assembly: Failed to create assembly: Error creating assembly
archive bin: Problem
Just curious, I assume if this change is made, would it only apply to
master branch?
-Mikhail
On Wed, Jul 29, 2015 at 2:09 PM, Andrew Purtell
andrew.purt...@gmail.com wrote:
@dev is now CCed
I didn't want to over structure the discussion with too much detail up front.
I do think CTR without
Elliott Clark created HBASE-14166:
-
Summary: Per-Region metrics can be stale
Key: HBASE-14166
URL: https://issues.apache.org/jira/browse/HBASE-14166
Project: HBase
Issue Type: Bug
Do we intentionally allow non-public comments on jira?
That is, currently commenters on our issue tracker can choose to restrict
their comments to the roles we've defined (like contributors, developers,
project admins, etc).
Comments so restricted do not go to the issues@hbase list and so don't
@dev is now CCed
I didn't want to over structure the discussion with too much detail up front. I
do think CTR without supporting process or boundaries can be more problematic
than helpful. That could take the form of customarily waiting for reviews
before commit even under a CTR regime. I
For Java 8, the following commands work:
1018 mvn clean install -DskipTests -Prelease,build-with-jdk8
-DcompileSource=1.8
1020 mvn install assembly:single -DskipTests -Prelease,build-with-jdk8
-DcompileSource=1.8
FYI
On Wed, Jul 29, 2015 at 11:21 AM, Ted Yu yuzhih...@gmail.com wrote:
If
I also think that's hard to justify. Anyone have a good reason?
On Wed, Jul 29, 2015 at 6:25 PM, Sean Busbey bus...@cloudera.com wrote:
A commenter expressly has to change the visibility when posting the
comment.
--
Sean
On Jul 29, 2015 5:59 PM, Andrew Purtell andrew.purt...@gmail.com
Had this thought after getting back on the road. As an alternative to any
sweeping change we could do one incremental but very significant thing that
acknowledges our status as trusted and busy peers: After posting a patch to
JIRA, after one week if there is no review or veto, a committer can
Really apprciate it Ted. Not sure why it was notworking, with a clean
checkout today it started working. May be some issues in my work branch.
Regards
Ram
On Thu, Jul 30, 2015 at 12:09 AM, Ted Yu yuzhih...@gmail.com wrote:
For Java 8, the following commands work:
1018 mvn clean install
Is there a way to disable changing visibility for comments on HBase JIRA ?
Cheers
On Wed, Jul 29, 2015 at 6:25 PM, Sean Busbey bus...@cloudera.com wrote:
A commenter expressly has to change the visibility when posting the
comment.
--
Sean
On Jul 29, 2015 5:59 PM, Andrew Purtell
Francis Liu created HBASE-14169:
---
Summary: API to refreshSuperUserGroupsConfiguration
Key: HBASE-14169
URL: https://issues.apache.org/jira/browse/HBASE-14169
Project: HBase
Issue Type: New
I agree, JIRA comments should be exclusively public. Doesn't someone have to
change comment visibility from default to restrict? Or did a default change ?
On Jul 29, 2015, at 1:41 PM, Sean Busbey bus...@cloudera.com wrote:
Do we intentionally allow non-public comments on jira?
That is,
A commenter expressly has to change the visibility when posting the comment.
--
Sean
On Jul 29, 2015 5:59 PM, Andrew Purtell andrew.purt...@gmail.com wrote:
I agree, JIRA comments should be exclusively public. Doesn't someone have
to change comment visibility from default to restrict? Or did
cuijianwei created HBASE-14165:
--
Summary: The initial size of RWQueueRpcExecutor.queues should be
(numWriteQueues + numReadQueues + numScanQueues)
Key: HBASE-14165
URL:
14 matches
Mail list logo
