Congrats, Yuqi!
-Todd
On Tue, Jun 6, 2023 at 11:01 AM Alexey Serbin
wrote:
> Congratulations, Yuqi!
>
> Thank you for your contribution to the project!
> I look forward to seeing more of that coming from you as a committer and
> PMC member :)
>
>
> Kind regards,
>
> Alexey
>
> On Tue, Jun 6,
Congrats on the recognition of you work, Abhishek!
Todd
On Wed, Feb 22, 2023, 6:15 PM 邓科 wrote:
> Congrats Abhishek!!!
>
> Yingchun Lai 于2023年2月23日周四 08:05写道：
>
> > Congrats!
> >
> > Mahesh Reddy 于2023年2月23日 周四03:07写道：
> >
> > > Congrats Abhishek!!! Great work and well deserved!
> > >
> > >
Sent an invite.
-Todd
On Mon, Jun 21, 2021 at 4:06 PM Bankim Bhavsar wrote:
> Hello Kudu devs,
>
> Could anybody add me to the kudu-python project on Pypi.org? Need this for
> uploading kudu-python artifacts for 1.15.0
>
> https://pypi.org/project/kudu-python/#history
>
entOS 7 (with devtoolset gcc)
> >- CentOS 8
> >- RHEL 6 (deprecated)
> > - RHEL 7 (with devtoolset gcc)
> >- RHEL 8
> >- Ubuntu 14.04 (deprecated)
> >- Ubuntu 16.04
> >- Ubuntu 18.04
> >- Debian 8 (deprecated)
> >- Debian 9
> >- SLES 12 (with toolchain gcc)
> >
> > Please provide your feedback, suggestions, or agreement on this proposal.
> >
> > Thank you,
> > Grant
> >
>
--
Todd Lipcon
Software Engineer, Cloudera
ient with --time_source=builtin, of course.
>
> I'll document options 3 and 4 in upstream JIRAs. If we see more value for
> Kudu users in making 'builtin' the default time source, we can reconsider
> and move forward with option 3 or 4 (or some other option).
>
> Let me know
lease notes
> for
> > > 1.12 release, of course. Also, there is some risk of hitting a not-yet
> > > detected bug in the built-in NTP client.
> > >
> > > Do you think the benefits of removing the requirement to have the local
> > > clock synchronized by local NTP server outweighs the drawbacks of
> adding an
> > > extra configuration step during 1.12 upgrade for Kudu clusters isolated
> > > from the Internet?
> > >
> > > Your feedback is highly appreciated!
> > >
> > >
> > > Thanks,
> > >
> > > Alexey
> > >
> > >
> > > P.S. I sent the original message one week ago, but it seems it went
> into
> > > spam box or alike, so I'm re-sending it.
> > >
> >
> >
> > --
> > Grant Henke
> > Software Engineer | Cloudera
> > gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
>
--
Todd Lipcon
Software Engineer, Cloudera
ions by next Wednesday I’ll go
> ahead and file an INFRA ticket.
>
--
Todd Lipcon
Software Engineer, Cloudera
gt;
> --
> Grant Henke
> Software Engineer | Cloudera
> gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
>
--
Todd Lipcon
Software Engineer, Cloudera
Hi Kudu community,
I'm happy to announce that the Kudu PMC has voted to add Yingchun Lai as a
new committer and PMC member.
Yingchun has been contributing to Kudu for the last 6-7 months and
contributed a number of bug fixes, improvements, and features, including:
- new CLI tools (eg 'kudu table
Thanks Mike for fixing this up and for the update.
Todd
On Mon, Mar 25, 2019, 10:31 PM Mike Percy wrote:
> Hi all,
> Kudu Jenkins is back up and running. Here is a summary of the changes I
> made to the underlying docker images:
>
>- Upgraded the Jenkins master to Jenkins 2.164.1 (latest
that keep CI working (e.g. pinning of unpinned Python
> dependencies that break).
> - Fixes to security vulnerabilities.
> - Data loss fixes.
> - Performance fixes, provided the impact:risk ratio is very high.
>
> What do you think?
>
--
Todd Lipcon
Software Engineer, Cloudera
t;>>>> >
>>>>> > Cons:
>>>>> > - New workflow for existing contributors
>>>>> > - WIP patches need to be migrated
>>>>> > - Effort involved to migrate
>>>>> >- Notifications
>>>>> >- Jenkins
>>>>> >
>>>>> > What do you think? Is this something worth changing? What are the
>>>>> benefits
>>>>> > and drawbacks?
>>>>> >
>>>>> > Thank you,
>>>>> > Grant
>>>>> > --
>>>>> > Grant Henke
>>>>> > Software Engineer | Cloudera
>>>>> > gr...@cloudera.com | twitter.com/gchenke |
>>>>> linkedin.com/in/granthenke
>>>>> >
>>>>>
>>>>
>>>>
>>>> --
>>>> Grant Henke
>>>> Software Engineer | Cloudera
>>>> gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
>>>>
>>>
>>>
>>> --
>>> Grant Henke
>>> Software Engineer | Cloudera
>>> gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
>>>
>>
>>
>> --
>> Grant Henke
>> Software Engineer | Cloudera
>> gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
>>
>
>
> --
> Grant Henke
> Software Engineer | Cloudera
> gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
>
--
Todd Lipcon
Software Engineer, Cloudera
_..." type flags. These kinds of
faults are a bit more realistic since after a node crashes it will have to
restart, go back to initial states, etc. It also ensures that we get
correlated-in-time failures across all different RPCs headed for the host,
which can trigger interesting behavior on
ure
> > > > information
> > > > is sent to this server (passwords)
> > > >
> > > > The newest Chrome release will show warnings when connecting to
> http://
> > > > sites[1], so I think it's about time to fix these and I'd like to
> &
n
> wrote:
>
> > Slightly related...
> >
> > Such a build could in theory be easily turned into a docker image too
> using
> > the relatively new Jib tool from Google:
> >
> >
> > https://cloudplatform.googleblog.com/2018/07/introducing-jib-build-ja
> > kudu:minicluster:1.x.x" as part of the release cycle?
> >
> > Thanks again,
> > Tim
> >
> > [1] https://github.com/MartinWeindel/kudu-docker
> > [2] https://kudu.apache.org/docs/quickstart.html#quickstart_vm
> > [3] https://g
log.info("%s is not a number. Not
> sending",
> value)
> self.metrics_client.flush(timestamp=collection_time)
> except Exception as ex:
> log.error("Failed to parse kudu metrics", ex)
> log.info("Pausing for 10 seconds after processing metrics")
> self.shutdown_event.wait(10)
>
The above snippet looks pretty reasonable to me.
Todd
--
Todd Lipcon
Software Engineer, Cloudera
uster
> 3d113b9b3 Bump version to 1.7.1-SNAPSHOT
>
> Attila
>
> On 2018. May 9., at 20:13, Todd Lipcon <t...@cloudera.com> wrote:
>
> Hey Attila,
>
> Is this a regression from 1.7.0 for you? If not, I don't think it should
> block the maintenance release. We can alwa
was that we weren't 100% clean and I wanted to be
able to split up all the fixes into separate patches.
-Todd
--
Todd Lipcon
Software Engineer, Cloudera
Grant has separately been working on enabling
SpotBugs and fixing the errors that it finds. I'll let him follow up if
there's anything devs need to know about that.
Thanks
-Todd
--
Todd Lipcon
Software Engineer, Cloudera
two builds is a pain,
> so the Maven build should be removed at some point.
>
> Please let me know your thoughts on the above proposal and plan.
>
> Thank you,
> Grant
> --
> Grant Henke
> Software Engineer | Cloudera
> gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
>
--
Todd Lipcon
Software Engineer, Cloudera
t; > not planning to add Python at first but it should go in there
> eventually.
> > >
> > > The current proposal is to have a new top level directory /examples,
> with
> > > the Java and Spark example code completely separate from the Java and
> > Spar
rprised if that caused
us to get blacklisted unless we took some effort to ensure that
miniclusters "reuse" some NTP state instead of resynchronizing at startup.
>
> On Fri, Mar 23, 2018 at 9:58 AM, Todd Lipcon <t...@cloudera.com> wrote:
> > It seems that over recent we
o 4 days instead.
>
> Thank you,
> Grant
>
>
> --
> Grant Henke
> Software Engineer | Cloudera
> gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
>
--
Todd Lipcon
Software Engineer, Cloudera
-itest --gtest_filter=Foo
Also, if you use 'ctest' to run tests, you'll notice that they are now
sharded which should make them run a bit faster and avoid timeouts.
Feel free to ping me if you hit any issues with precommits or dev workflows.
-Todd
--
Todd Lipcon
Software Engineer, Cloudera
r to fs_data_dirs, which is nice. If the metadata directory
> can't be found in directory specified by this gflag (or in the WAL
> directory, if blank), we can fall back to looking in the first data
> directory.
>
That sounds reasonable to me.
-Todd
--
Todd Lipcon
Software Engineer, Cloudera
Our board report is due tomorrow. Here's a draft. I'll operate on lazy
consensus -- let me know if you want any changes, otherwise will post as is.
Apache Kudu is a distributed columnar storage engine built for the Apache
Hadoop ecosystem.
## Issues:
No issues requiring the board's attention
r*
>> the
>> Thanksgiving holiday in the US, and to start a vote on RC1 a couple of
>> days
>> after that.
>>
>> Devs: That means release notes for notable changes in 1.6 should be up for
>> review and ready to go by Monday, November 27 (the Monday after
>>
on the ASF slack in case we decide to go
> forward with this. If we don't decide to go forward with it, it's a good
> idea to hold onto the channel and pin a message in there about how to get
> to the "official" Kudu slack.
>
> On Mon, Oct 23, 2017 at 3:00 PM, Todd Lipcon <t...@cl
in) across the assigned
data disks. Thanks for clarifying.
-Todd
> Thanks!
>
> Best,
> Hao
>
> On Mon, Sep 4, 2017 at 10:10 PM, Todd Lipcon <t...@cloudera.com> wrote:
>
> > Quick question on the fix: does the lifo behavior now cause the entirety
> of
> > the c
Quick question on the fix: does the lifo behavior now cause the entirety of
the copied tablet to end up in one container (hence one disk) if the tablet
is less than a few gb? If so that also seems like a regression to consider.
(Sorry for hijacking this thread rather than commenting on Gerrit. On
> Review: http://gerrit.cloudera.org:8080/7749
>
> Thanks!
> Tony
>
--
Todd Lipcon
Software Engineer, Cloudera
ly submitted a few thousand each time, the speed is too
> slow.
>
I think using AUTO_FLUSH_BACKGROUND should be your best bet. Are you
getting the buffer errors while configured for AUTO_FLUSH_BACKGROUND?
>
>
>
>
>
>
> At 2017-08-15 03:56:10, "Todd Lipcon" <
cture
> for more end-to-end tests).
>
> I'd be interested in hearing thoughts. In running these verification tasks
> like Jepsen, are we getting coverage that we wouldn't get in our own
> integration tests? And how is our test coverage for disk corruption?
>
> --
> Andrew Wong
>
--
Todd Lipcon
Software Engineer, Cloudera
ger builds
using http://jenkins.kudu.apache.org/gerrit_manual_trigger/ (seems to work
fine even when the automatic trigger gets stuck)
-Todd
On Thu, Jun 29, 2017 at 11:22 AM, Todd Lipcon <t...@cloudera.com> wrote:
> For some reason Jenkins stopped auto-triggering builds last night. Not
its thing.
-Todd
--
Todd Lipcon
Software Engineer, Cloudera
Hey folks,
Looks like our flaky tests have gotten pretty out of hand again, with 6 or
7 of the suites >4% flaky.
Can we get some volunteers to diagnose and fix up these worst offenders?
I'll volunteer for log_rolling-itest and alter_table-test.
-Todd
--
Todd Lipcon
Software Engineer, Cloudera
Hi,
The Apache Kudu team is happy to announce the first release candidate for
Apache Kudu 1.4.0.
Apache Kudu 1.4.0 is a minor release which offers many improvements and
fixes since the prior release. This first release candidate does not
contain full release notes -- I am hoping that we can
tRestartWithOrphanedReplicates ").
>
>
> On Mon, May 22, 2017 at 12:15 PM, Todd Lipcon <t...@apache.org> wrote:
> > BTW should also add: if you've authored any major improvements or
> important
> > bug fixes since 1.3, please start thinking about release notes (eg crea
2, 2017 at 7:42 PM, Mike Percy <mpe...@apache.org> wrote:
> It would be nice to rename TabletPeer. What do you guys think? It's kind of
> a confusingly named class.
>
> I think a better class name would be ReplicatedTablet or TabletReplica.
>
> Mike
>
--
Todd Lipcon
Software Engineer, Cloudera
useful to
> > > provide users a way to whitelist any 'trusted' but publicly IP address.
> > So
> > > that unauthenticated
> > > connections coming from those public IP addresses will not be rejected.
> > >
> > > One way I am proposing here, is to provide a Gflag that can take a list
> > of
> > > subnet (in CIDR notation).
> > > And consider those subnet as trusted and do not refuse any
> > unauthenticated
> > > connections.
> > >
> > > Please let me know your thoughts or if you have any alternatives in
> mind.
> > > Thanks a lot!
> > >
> > > Best,
> > > Hao
> > >
> >
>
--
Todd Lipcon
Software Engineer, Cloudera
everything
> > on CentOS 6.6 in release mode, ran all the tests, they passed. Same for
> > Java.
> >
> > J-D
> >
> > On Wed, Apr 12, 2017 at 10:15 PM, Todd Lipcon <t...@apache.org> wrote:
> >
> >> Hi,
> >>
> >> The Apache
Need these two patches committed before I can tag the RC:
https://gerrit.cloudera.org/6621/
https://gerrit.cloudera.org/6622/
If someone can take a look tonight I'll build the RC for a vote, otherwise
will do so tomorrow AM.
-Todd
On Wed, Apr 12, 2017 at 7:04 PM, Todd Lipcon &l
Putting together the release candidate now, will send out a vote soon.
On Wed, Apr 12, 2017 at 2:58 PM, Alexey Serbin <aser...@cloudera.com> wrote:
> On 4/12/17 2:56 PM, Todd Lipcon wrote:
>
> On Wed, Apr 12, 2017 at 2:54 PM, Alexey Serbin <aser...@cloudera.com>
>> wr
t;
>
> On 4/12/17 2:43 PM, Jean-Daniel Cryans wrote:
>
>> +1
>>
>> Nothing else comes to mind. Kudos for finding the bug.
>>
>> J-D
>>
>> On Wed, Apr 12, 2017 at 2:42 PM, Todd Lipcon <t...@cloudera.com> wrote:
>>
>> This morning we
that point-releases like this should be critical fixes (data loss,
incorrect results, crashes, etc) only.
-Todd
--
Todd Lipcon
Software Engineer, Cloudera
The Apache Kudu team is happy to announce the release of Kudu 1.3.0.
Kudu is an open source storage engine for structured data which supports
low-latency random access together with efficient analytical access
patterns. It is designed within the context of the Apache Hadoop ecosystem
and supports
With four binding +1s, this vote passes. I'll take care of staging the
release, etc, over the next day or two, but probably will hold off to
Monday to announce so people don't miss it over the weekend.
-Todd
On Thu, Mar 16, 2017 at 8:48 AM, Todd Lipcon <t...@cloudera.com> wrote:
AM PDT.
Thanks,
Todd
--
Todd Lipcon
Software Engineer, Cloudera
Mar 10, 2017, at 5:28 PM, Adar Dembo <a...@cloudera.com> wrote:
> >
> > I'll put out a patch to strip the NO_FATALS() that are triggering the
> > compilation error in gcc5.
> >
> > No idea _why_ it's happening though; I think Mike will look into that.
> >
>
y-itest fail on OS X 10.10 (fixed
> > on master in c5ec0ddb0
> > <https://github.com/apache/kudu/commit/c5ec0ddb01da87de4a037a4879a4ef
> 92c434930f>
> > )
> > - verified signature
> >
> > I don't think we should hold the release over macOS test issues, but if
> we
> >
On Thu, Mar 9, 2017 at 10:36 PM, Todd Lipcon <t...@apache.org> wrote:
> Hi,
>
> The Apache Kudu team is happy to announce the first release candidate for
> Apache Kudu 1.3.0.
>
> Apache Kudu 1.3 is a minor release which adds various new features,
> improvements, b
Hi,
The Apache Kudu team is happy to announce the first release candidate for
Apache Kudu 1.3.0.
Apache Kudu 1.3 is a minor release which adds various new features,
improvements, bug fixes, and optimizations on top of Kudu 1.2. Highlights
include significantly improved support for security,
with a real fix, Dan just posted numbers and they don't look too
> bad. If you haven't closed the branch I'd pull it in.
>
> On Thu, Mar 9, 2017 at 2:07 PM, Todd Lipcon <t...@apache.org> wrote:
>
> > Please take a look at release notes review here:
> > https://gerrit.
Please take a look at release notes review here:
https://gerrit.cloudera.org/#/c/6334/
I think that's the last remaining bit.
-Todd
On Thu, Mar 9, 2017 at 12:06 PM, Todd Lipcon <t...@apache.org> wrote:
> Hi folks,
>
> I'd like to cut the first release candidate for Kudu 1.3 la
Hi folks,
I'd like to cut the first release candidate for Kudu 1.3 later today. I've
just posted a review to fix some RAT tool issues in 1.3, and currently
working on a draft of the release notes.
Having chatted with a few people with open JIRAs, it sounds like there are
no further release
mmunities would
> >> like to pursue in earnest, I would be happy to work with you on next
> >> steps. I would suggest that we start with something small so that we
> >> could address the necessary build toolchain changes, and develop a
> >> workflow for moving around code and tests, a protocol for code reviews
> >> (e.g. Gerrit), and coordinating ASF releases.
> >>
> >
> > I think, if I'm reading this correctly, that you're assuming integration
> > with the 'downstream' projects (e.g. Impala and Kudu) would be done via
> > their toolchains. For something as fast moving as utility code - and
> > critical, where you want the latency between adding a fix and including
> it
> > in your build to be ~0 - that's a non-starter to me, at least with how
> the
> > toolchains are currently realised.
> >
> > I'd rather have the source code directly imported into Impala's tree -
> > whether by git submodule or other mechanism. That way the coupling is
> > looser, and we can move more quickly. I think that's important to other
> > projects as well.
> >
> > Henry
> >
> >
> >
> >>
> >> Let me know what you think.
> >>
> >> best
> >> Wes
> >>
>
--
Todd Lipcon
Software Engineer, Cloudera
revert the change.
-Todd
--
Todd Lipcon
Software Engineer, Cloudera
one else feels like taking a
turn.
Any comments or concerns?
-Todd
--
Todd Lipcon
Software Engineer, Cloudera
I vote for #1, though #3 is reasonable
> too.
>
OK, I'll go with #1. I tested that the patch applies cleanly and fixes a
manufactured test case I wrote.
>
> On Tue, Feb 14, 2017 at 6:09 PM, Todd Lipcon <t...@cloudera.com> wrote:
> > BTW, I should add that libstdcxx
BTW, I should add that libstdcxx as included in gcc 4.9.2 (devtoolset on
el6) doesn't have this bug, since it just wraps pthread_once. So, it's
probably not a _real_ issue since we don't use libc++ for production builds.
-Todd
On Tue, Feb 14, 2017 at 6:05 PM, Todd Lipcon <t...@cloudera.
on a local machine came to me after I sent that e-mail.
> Sorry for the noise.
>
> On Fri, Feb 10, 2017 at 10:30 AM, Todd Lipcon <t...@cloudera.com> wrote:
>
> > On Fri, Feb 10, 2017 at 10:14 AM, Alexey Serbin <aser...@cloudera.com>
> > wrote:
> >
> &g
On Fri, Feb 10, 2017 at 10:29 AM, Dan Burkert <danburk...@apache.org> wrote:
> On Fri, Feb 10, 2017 at 10:02 AM, Todd Lipcon <t...@cloudera.com> wrote:
> >
> > Yea, but still the best number here is 685MB/sec. Assuming 2ghz, that's
> > around 3 cycles/byte (~
l.com/sites/default/files/m/d/4/1/d/8/10TB24_Breakthrough_AES_Performance_with_Intel_AES_New_Instructions.final.secure.pdf
-Todd
>
> On Thu, Feb 9, 2017 at 10:22 PM, Todd Lipcon <t...@cloudera.com> wrote:
>
> > Hey folks,
> >
> > For those not following along,
M (because the handshake would fail)
and be trivially zero-overhead. Am I missing any big issues with this idea?
Anyone got a better one?
-Todd
--
Todd Lipcon
Software Engineer, Cloudera
f
the 'common' group and not the 'uninstrumented' group.
Mike, can you take a look at this? Or can we revert your patch for the time
being until it's sorted out? Seems to be corrupting workspaces left and
right (more than the problem it's meant to solve was)
-Todd
On Wed, Feb 1, 2017 at 10:10 PM, Todd Lipcon <t
Hi Kudu devs,
Forwarding this from the infrastructure folks who run the gerrit used by
Kudu. See below.
-Todd
-- Forwarded message --
There will be a 1-hour maintenance window from 7pm PST to 8pm PST on Wednesday,
Feb 1st to update Gerrit (https://gerrit.cloudera.org) from
t; > >> understand. In that case, even if the token signature is correct, the
> > >> older code should not accept the new token since unsupported
> non-compat
> > >> feature flags is present.
> > >>
> > >> But in the essence this looks great, IM
he essence this looks great, IMO.
> >
> >
> > Best regards,
> >
> > Alexey
> >
> > On Wed, Jan 25, 2017 at 12:52 PM, Todd Lipcon <t...@cloudera.com> wrote:
> >
> >> Actually had one more idea... how about:
> >> message Authent
ould fail.
> On Wed, Jan 25, 2017 at 12:37 PM, Todd Lipcon <t...@cloudera.com> wrote:
>
>> Hey folks
>>
>> I'm working on the token signing/verification stuff at the moment.
>> Curious to solicit some opinions on this:
>>
>>
>> message TokenPB
signing_key_seq_num = 4;
};
On Wed, Jan 25, 2017 at 12:44 PM, Todd Lipcon <t...@cloudera.com> wrote:
> On Wed, Jan 25, 2017 at 12:40 PM, Dan Burkert <d...@cloudera.com> wrote:
>
>> I think it must go in the 'token_contents' itself, otherwise it can be
>> modified by a malicious c
to be signing
something like a concatenation of 'token_contents + signature'. Not too
hard to construct this concatenation, but it does add some complexity.
Any strong opinions either way?
-Todd
--
Todd Lipcon
Software Engineer, Cloudera
hink for a long time we resisted vendoring boost, and so avoiding the
> > dynamically linked parts of boost was advantageous to avoid
> > incompatibilities in system boost versions. I recall we are vendoring
> > boost now, so that should be less of a concern, I would think.
&g
The Apache Kudu team is happy to announce the release of Kudu 1.2.0.
Kudu is an open source storage engine for structured data which supports
low-latency random access together with efficient analytical access
patterns. It is designed within the context of the Apache Hadoop ecosystem
and supports
should be less of a concern, I would think.
> >
> > - Dan
> >
> > On Thu, Jan 19, 2017 at 4:16 PM, Todd Lipcon <t...@cloudera.com> wrote:
> >
> >> Hey folks,
> >>
> >> I'm starting to look at implementing a 96-bit timestamp type that w
Hi,
The Apache Kudu team is happy to announce the first release candidate for
Apache Kudu 1.2.0.
Apache Kudu 1.2 is a minor release which adds various new features,
improvements, bug fixes, and optimizations on top of Kudu 1.1. Please see
the release notes for details. Thanks to the 18
configure doxygen or annotate the declaration to
avoid generating this doc?
Another odd example is the following:
https://kudu.apache.org/cpp-client-api/structStubsCompileAssert.html
-Todd
--
Todd Lipcon
Software Engineer, Cloudera
decade of community accomplishments
> cloudera.com/hadoop10
> #hadoop10
>
>
>
--
Todd Lipcon
Software Engineer, Cloudera
resto* distributed querying tool .. Does Kudu has Presto
> Support ? If not , I will go ahead and Create JIRA to track this.. Also
> would like to contribute on the same ..
>
> Pls throw some points
>
> Cheers,
> Senthil
>
--
Todd Lipcon
Software Engineer, Cloudera
good hint they probably aren't
that critical and we should downgrade to major.
Let's also start working on docs and release notes for 1.2 this week. I
think we have a number of changes that are worth highlighting, and it seems
we don't have any noted in docs/release_notes.adoc yet.
-Todd
--
to Java8 by default,
I can adjust the kudu-gerrit job config to put them on the path.
The paths are:
/opt/apache-maven-3.3.9/bin
and:
JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/
(bin/ directory inside)
-Todd
--
Todd Lipcon
Software Engineer, Cloudera
Things seem to be working OK, please ping me if anything seems amiss.
-Todd
On Mon, Dec 12, 2016 at 2:28 PM, Todd Lipcon <t...@cloudera.com> wrote:
> Hey folks,
>
> The version of Jenkins we've been running for a while has some remote code
> execution exploits, apparently.
Hey folks,
The version of Jenkins we've been running for a while has some remote code
execution exploits, apparently. So, I'm upgrading to the latest at the
moment. Should be done in the next 10-15 minutes unless something goes
wrong :)
--
Todd Lipcon
Software Engineer, Cloudera
t; J-D
> >
> > On Tue, Dec 6, 2016 at 8:44 PM, Todd Lipcon <t...@apache.org> wrote:
> >
> > > Hi Kudu developers,
> > >
> > > Back in mid-October I proposed a plan for the 1.1 and 1.2 releases[1].
> > 1.1
> > > is now behind us, so I
Hi Kudu developers,
Back in mid-October I proposed a plan for the 1.1 and 1.2 releases[1]. 1.1
is now behind us, so I wanted to start a thread regarding 1.2.
The original proposal was to aim for a 1.2 release for mid-January. While
it was always planned to be a time-based release, we also
able on generated source.
>>
>> On Wed, Nov 23, 2016 at 12:59 Todd Lipcon <t...@cloudera.com> wrote:
>>
>> > Ping?
>> >
>> > On Sun, Nov 20, 2016 at 7:53 PM, Todd Lipcon <t...@cloudera.com> wrote:
>> >
>> > Hey folks,
&g
, 51962 appear to be in generated code :)
So, a few questions:
1) can we get the checkstyle output to go to a separate file instead of the
console?
2) can we disable checkstyle on generated sources?
-Todd
--
Todd Lipcon
Software Engineer, Cloudera
Hi,
The Apache Kudu team is happy to announce the first release candidate for
Apache Kudu 1.1.0.
Apache Kudu 1.1 is a minor release which adds various new features,
improvements, bug fixes, and optimizations on top of Kudu 1.0. Please see
the release notes for details.
The is a source-only
take a look.
-Todd
On Mon, Nov 14, 2016 at 3:30 PM, Alexey Serbin <aser...@cloudera.com> wrote:
> That makes sense to me.
>
>
> Best regards,
>
> Alexey
>
>
> On Mon, Nov 14, 2016 at 3:05 PM, Todd Lipcon <t...@cloudera.com> wrote:
>
> > Hey folks,
&
re_acceptor_hostname = true
>
We've actually already got that there. But it doesn't help -- the issue is
that the client can't figure out what realm it's connecting to in krb 1.10
>
>
> Best regards,
>
> Alexey
>
> On Mon, Nov 7, 2016 at 3:42 PM, Todd Lipcon <t...@cloudera.co
importing new dependencies/build complexity.
-Todd
On Mon, Nov 7, 2016 at 6:49 PM, Todd Lipcon <t...@cloudera.com> wrote:
> On Mon, Nov 7, 2016 at 4:35 PM, Alexey Serbin <aser...@cloudera.com>
> wrote:
>
>> Ah, I see -- thank you for the clarification.
>>
>&g
FWIW it looks like there's already some code out there that can do the
appropriate "fake DNS" wrapping: https://cwrap.org/nss_wrapper.html
On Sun, Nov 6, 2016 at 9:13 PM, Todd Lipcon <t...@cloudera.com> wrote:
> Hey folks
>
> I've been looking into why our kerberos-de
IASES only does forward DNS).
Any other ideas?
-Todd
--
Todd Lipcon
Software Engineer, Cloudera
we're safe to move forward.
I also added some content to our docs here:
https://gerrit.cloudera.org/#/c/4905/
-Todd
On Mon, Oct 31, 2016 at 12:29 PM, Todd Lipcon <t...@cloudera.com> wrote:
> Hey devs,
>
> I've been looking at this page this morning:
> https://www.apache.o
t 30m or so thinking about this, so maybe I missed a better
option? Feedback appreciated.
I'm leaning towards option 3 here, but would appreciate feedback before I
go too far down that path.
-Todd
--
Todd Lipcon
Software Engineer, Cloudera
integrate with OpenSSL.
I'll do a little further reading on this topic, but please hold off on
pushing any SSL-related code until we've determined whether this is
necessary. Of course code reviews can continue :)
-Todd
--
Todd Lipcon
Software Engineer, Cloudera
t; scope doc, and have come up with some alternatives. You can see the
> > alternative and discussion here:
> >
> > https://docs.google.com/document/d/1Yu4iuIhaERwug1vS95yWDd_
> > WzrNRIKvvVGUb31y-_mY/edit#
> >
> > - Dan
> >
> > On Mon, Oct 10, 2016 a
-8 weeks after 1.1). My hope is that we can get a good chunk of the
security features that folks have started looking at done by then, as well
as various other work that people have been circulating design docs for.
I'll also volunteer to RM these two releases.
Thanks
-Todd
--
Todd Lipcon
Software
Hey folks,
I'm hoping to start breaking down some tasks from this document in the next
couple days. If you were planning to take a look, please try to do so soon.
-Todd
On Mon, Oct 3, 2016 at 5:33 PM, Todd Lipcon <t...@cloudera.com> wrote:
> Hi all,
>
> Now that we've r
whole log is available here:
https://gist.githubusercontent.com/toddlipcon/466976caf973f496885da9efc2f7246c/raw/f9baf418dad4ad07f33961b131c86e84803815a8/alter_table-randomized-test.txt
Any ideas what might be causing this out-of-order result? Is the test
making some incorrect assumptions or might we
1 - 100 of 112 matches
Mail list logo
