Thanks for the response. You got my question correctly.
If we are scanning the rows one by one and we have the requested column in
the column tracker, we have the row+column to look up in the bloom filter,
don't we? We may not be able to filter out the file scanners upfront. But
may at the later t
Sorry, this is the one. https://issues.apache.org/jira/browse/HBASE-14917
On Wed, Dec 2, 2015 at 9:21 PM, Apekshit Sharma wrote:
> https://issues.apache.org/jira/browse/HBASE-14916
>
> On Wed, Dec 2, 2015 at 7:52 PM, Ted Yu wrote:
>
>> Getting result of 3 would mean that anti pattern check and
https://issues.apache.org/jira/browse/HBASE-14916
On Wed, Dec 2, 2015 at 7:52 PM, Ted Yu wrote:
> Getting result of 3 would mean that anti pattern check and
> BuildWithHadoopVersions
> check failed.
>
> Echoing result at the end of each step is good.
>
> Cheers
>
> On Wed, Dec 2, 2015 at 7:48 PM
The Jenkins job would checkout the main repo's master branch, run 'mvn
clean site site:stage' to generate the site, docs, and APIdocs. Then it
would checkout the asf-site branch of the hbase-site repo (or whetever it
is called) and commit the newly-generated target/stage/* to it and push.
Does that
Appy created HBASE-14917:
Summary: Log in console if individual tests in test-patch.sh fail
or pass.
Key: HBASE-14917
URL: https://issues.apache.org/jira/browse/HBASE-14917
Project: HBase
Issue Type
Getting result of 3 would mean that anti pattern check and
BuildWithHadoopVersions
check failed.
Echoing result at the end of each step is good.
Cheers
On Wed, Dec 2, 2015 at 7:48 PM, Apekshit Sharma wrote:
> I was staring at test-patch.sh for 15 minutes, but couldn't figure out what
> could h
I was staring at test-patch.sh for 15 minutes, but couldn't figure out what
could have been the error. Made sure that if any function was returning 1,
it was adding something JIRA_COMMENT. Tried to test it locally echoing
RESULT value after every test but it didn't help because our jenkins
environm
-1 is given if value of $RESULT is not 0 :
submitJiraComment $RESULT
$RESULT is summation of return values of various checks:
checkAntiPatterns
(( RESULT = RESULT + $? ))
checkBuildWithHadoopVersions
(( RESULT = RESULT + $? ))
...
Looks like $RESULT was non-zeron somehow.
It was not clear whic
Hi
Any ideas what can be the reason here?
https://issues.apache.org/jira/browse/HBASE-14865?focusedCommentId=15037056&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15037056
-- Appy
Appy created HBASE-14916:
Summary: Add checkstyle_report.py to other branches
Key: HBASE-14916
URL: https://issues.apache.org/jira/browse/HBASE-14916
Project: HBase
Issue Type: Bug
Report
Ok, so no annotation change then. I looked at HBASE-14769. Change there seems
fine.
> On Dec 2, 2015, at 5:03 PM, Apekshit Sharma wrote:
>
> In this particular case, we are deleting functions in HBaseAdmin which take
> byte[] or String as argument.
> HBASE-14769
>
> On Wed, Dec 2, 2015 at 4:5
In this particular case, we are deleting functions in HBaseAdmin which take
byte[] or String as argument.
HBASE-14769
On Wed, Dec 2, 2015 at 4:56 PM, Andrew Purtell
wrote:
> We also might want to fix the annotation. Like Stack said it depends on
> the particulars. I suggest filing a JIRA.
>
> >
We also might want to fix the annotation. Like Stack said it depends on the
particulars. I suggest filing a JIRA.
> On Dec 2, 2015, at 4:36 PM, Stack wrote:
>
> Appy makes a pretty good argument.
>
> What in particular are we discussing Ashish?
>
> Thanks,
> St.Ack
>
>> On Wed, Dec 2, 2015
Appy makes a pretty good argument.
What in particular are we discussing Ashish?
Thanks,
St.Ack
On Wed, Dec 2, 2015 at 3:49 PM, Apekshit Sharma wrote:
> I think it should be okay to remove them. When I imagine myself on other
> side, a dev using client api of Foo project, and I see a class retu
I think it should be okay to remove them. When I imagine myself on other
side, a dev using client api of Foo project, and I see a class returning
reference to an internal class, I would not trust that function. If I
really need something from returned ref, I'd probably use it, and if it
goes away t
Appy:
Nice work.
In dev-support/test-patch.sh :
mv target/site/checkstyle.css $PATCH_DIR
This seems to give the following in console:
Determining number of patched Checkstyle errors.
==
==
Hey,
Checkstyles have changed recently. And while they are small changes, they
do affect the codebase in big way as time progresses.
New checkstyles were added in HBASE-14829. Description of the jira lists
the new checks that were added. As of result of these new checks, our
checkstyle error count
stack created HBASE-14915:
-
Summary: Hanging test :
org.apache.hadoop.hbase.mapreduce.TestImportExport
Key: HBASE-14915
URL: https://issues.apache.org/jira/browse/HBASE-14915
Project: HBase
Issue Ty
As part of my continuing advocacy of builds.apache.org and that their
results are now worthy of our trust and nurture, here are some highlights
from the last few days of builds:
+ hadoopqa is now finding zombies before the patch is committed.
HBASE-14888 showed "-1 core tests. The patch failed the
With HBASE-14689 resolved, I plan to spin the next RC this weekend. Let me
know if you have any concerns.
-n
On Tue, Nov 17, 2015 at 8:33 PM, Andrew Purtell
wrote:
> Let's revert this from 0.98 even if the problem isn't manifesting there
> (or perhaps just not in the same way)
>
>
> > On Nov 17
Good by me. Interested in the answers to Nicks questions too.
St.Ack
On Wed, Dec 2, 2015 at 11:07 AM, Nick Dimiduk wrote:
> +1 in theory. How will this work with integration of javadoc into the site?
> How will RM's manage integrating site docs into their releases?
>
> On Wed, Dec 2, 2015 at 8:5
Nate Edel created HBASE-14914:
-
Summary: Move functionality needed to handle Snapshots without
RegionServer dependency
Key: HBASE-14914
URL: https://issues.apache.org/jira/browse/HBASE-14914
Project: HBas
Nate Edel created HBASE-14913:
-
Summary: Enable testing I/O without regionserver or threads.
Key: HBASE-14913
URL: https://issues.apache.org/jira/browse/HBASE-14913
Project: HBase
Issue Type: Sub
Nate Edel created HBASE-14911:
-
Summary: Move functionality needed to write HFiles without
RegionServer dependency
Key: HBASE-14911
URL: https://issues.apache.org/jira/browse/HBASE-14911
Project: HBase
Nate Edel created HBASE-14912:
-
Summary: Move functionality needed to read WAL without
RegionServer dependency
Key: HBASE-14912
URL: https://issues.apache.org/jira/browse/HBASE-14912
Project: HBase
Nate Edel created HBASE-14910:
-
Summary: Create base hbase-mapred and hbase-io modules, move
HTableInputFormat and HTableOutputFormat
Key: HBASE-14910
URL: https://issues.apache.org/jira/browse/HBASE-14910
+1 in theory. How will this work with integration of javadoc into the site?
How will RM's manage integrating site docs into their releases?
On Wed, Dec 2, 2015 at 8:56 AM, Sean Busbey wrote:
> Hi Folks!
>
> You may recall the occasional emails dev@ gets from a Jenkins job Misty
> set
> up to mak
[
https://issues.apache.org/jira/browse/HBASE-14909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-14909.
---
Resolution: Fixed
Assignee: stack
Fix Version/s: 1.3.0
1.2.0
stack created HBASE-14909:
-
Summary: NPE testing for RIT
Key: HBASE-14909
URL: https://issues.apache.org/jira/browse/HBASE-14909
Project: HBase
Issue Type: Sub-task
Components: test
Sounds good to me.
On Wed, Dec 2, 2015 at 9:00 AM, Andrew Purtell
wrote:
> No concerns here.
>
> > On Dec 2, 2015, at 8:56 AM, Sean Busbey wrote:
> >
> > Hi Folks!
> >
> > You may recall the occasional emails dev@ gets from a Jenkins job Misty
> set
> > up to make updating the website easier fo
stack created HBASE-14908:
-
Summary: TestRowCounter flakey especially on branch-1
Key: HBASE-14908
URL: https://issues.apache.org/jira/browse/HBASE-14908
Project: HBase
Issue Type: Sub-task
No concerns here.
> On Dec 2, 2015, at 8:56 AM, Sean Busbey wrote:
>
> Hi Folks!
>
> You may recall the occasional emails dev@ gets from a Jenkins job Misty set
> up to make updating the website easier for us. They're titled "HBase
> Generate Website" and they give a series of steps any commit
Hi Folks!
You may recall the occasional emails dev@ gets from a Jenkins job Misty set
up to make updating the website easier for us. They're titled "HBase
Generate Website" and they give a series of steps any committer can run to
push the changes live.
Misty has been investigating automating this
Build status: Successful
If successful, the website and docs have been generated. If failed, skip to the
bottom of this email.
Use the following commands to download the patch and apply it to a clean branch
based on origin/asf-site:
wget -O-
https://builds.apache.org/job/hbase_generate_webs
Jingcheng Du created HBASE-14907:
Summary: NPE of MobUtils.hasMobColumns in Build failed in Jenkins:
HBase-Trunk_matrix » latest1.8,Hadoop #513
Key: HBASE-14907
URL: https://issues.apache.org/jira/browse/HBASE-149
35 matches
Mail list logo
