g/content/repositories/orgapachekudu-1094/
> > > > >
> > > > > It is tagged in Git as 1.15.0-RC2 and the corresponding hash is the
> > > > > following:
> > > > >
> > > > >
> > > >
> > >
> >
> ht
refer if the release notes would be included in the released
> artifacts.
>
> Attila
>
--
Grant Henke
Software Engineer | Cloudera
gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
The Apache Kudu team is happy to announce the release of Kudu 1.14.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
> >> >> BugPattern: TypeParameterUnusedInFormals
> > >> >> Stack Trace:
> > >> >> java.lang.NoSuchFieldError: bound
> > >> >> at
> > >> >>
> > >>
> >
> com.google.errorprone.bugpatterns.TypeParameterUnusedInFormals.matc
t; > lot of memory.
> >
> > I agree with Grant that the issue pointed by Greg isn't a regression and
> > does not look like a release stopper, but it would be nice to update
> README
> > if it's decided to cut RC2 due to some other issue.
> >
> >
> > Kind rega
file or directory:
> '/home/gsolovyev/git/kudu/build/coverage/FacebookService.cpp'
>
>
> Greg
>
>
> On Wed, Jan 20, 2021 at 10:15 AM Grant Henke
> wrote:
>
> > Hello Kudu devs!
> >
> > The Apache Kudu team is happy to announce the first release candidate for
&
Hello Kudu devs!
The Apache Kudu team is happy to announce the first release candidate for
Apache
Kudu 1.14.0.
Apache Kudu 1.14.0 is a minor release that offers many improvements and
fixes
since Apache Kudu 1.13.0.
This is a source-only release. The artifacts have been staged here:
1:41 PM Greg Solovyev
> wrote:
>
> > +1. And, thanks for volunteering!
> > Greg
> >
> > On Mon, Dec 14, 2020 at 11:43 AM Andrew Wong >
> > wrote:
> >
> > > +1
> > >
> > > Thanks for volunteering! And thanks for accommodating
ures in Kudu but can't upgrade host operating
> systems
> > > in near future.
> > >
> > > Rest looks good to me and can't wait to start using the new C++
> features
> > > this will unlock.
> > >
> > > Thanks,
> > > -Bankim.
> > >
&
Hello Kudu developers and users!
The purpose of this email is to propose and collect feedback on changes to
the documented "Operating System Requirements"
on https://kudu.apache.org/docs/installation.html for the next Kudu release
(1.14.0).
There are a few goals to updating the documented
und here:
> > > https://github.com/apache/kudu/blob/1.13.0-RC2/docs/release_notes.adoc
> > >
> > > I'd suggest going through the release notes, building Kudu, and running
> > > the unit
> > > tests. Testing out the Maven repo would also be appreciated. Also, it's
> > > worth
> > > running Kudu Java tests against kudu-binary JAR artifact as described
> in
> > > the
> > > commit message here:
> > >
> > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=kudu.git;a=commit;h=8a6faaa93f3e206ac75e8087731daccaf7ab646a
> > >
> > > The vote will run until a majority[1] is achieved, but at least until
> > > Wednesday
> > > Sep 16th 9:00:00 CEST 2020, which is a bit over the suggested 72 hours
> > due
> > > to
> > > the weekend, to give everyone a chance to review this release candidate
> > and
> > > vote.
> > >
> > > Thank You,
> > > Attila
> > >
> > > [1] https://www.apache.org/foundation/voting.html#ReleaseVotes
> > >
> > >
> >
>
--
Grant Henke
Software Engineer | Cloudera
gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
you'd like to squeeze in
> to
> > this
> > > release so I propose cutting the branch on 8/14 Friday. This will give
> > us a
> > > little over two weeks.
> > >
> > > In turn, I'd like to get the release notes committed before we cut the
> > R
; > docs after the release if it's successful.
> >
> > Attila
> >
> > [1] https://github.com/apache/beam/releases
> > [2] https://github.com/apache/cloudstack/releases
> > [3] https://github.com/apache/pulsar/releases
> >
>
>
> --
> Andrew Wong
>
--
Grant Henke
Software Engineer | Cloudera
gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
/kudu/master/kudu-build-test-arm64-in-docker/175cda1/
> : RETRY_LIMIT in 1m 22s
>
--
Grant Henke
Software Engineer | Cloudera
gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
ps://logs.openlabtesting.org/logs/periodic-kudu-mail/github.com/apache/kudu/master/kudu-build-test-arm64-in-docker/52dfacd/
> : FAILURE in 10m 34s
>
--
Grant Henke
Software Engineer | Cloudera
gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
t; > to
> > >> document such issues, as well as catch these kinds of CI emails for
> the
> > >> time being.
> > >>
> > >> Other projects have similar "builds" mailing lists
> > >> <https://mail-archives.apache.org/mod_mbox/>; it doesn't seem
> > >> unreasonable
> > >> to start one for Kudu as well, so per the ASF Mailing List Moderation
> > >> guidelines <https://infra.apache.org/mailing-list-moderation.html>,
> I'm
> > >> surfacing this to discuss a bit here. If there's agreement on this
> > being a
> > >> useful list to have, I'll send out a request to create it.
> > >>
> > >>
> > >> Thanks,
> > >> Andrew
> > >>
> > >
> >
>
--
Grant Henke
Software Engineer | Cloudera
gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
enlabtesting.org/logs/periodic-kudu-mail/github.com/apache/kudu/master/kudu-build-test-arm64-in-docker/5751add/
> : FAILURE in 2h 44m 46s
>
--
Grant Henke
Software Engineer | Cloudera
gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
Subprocess.java:291)
On Thu, Jul 16, 2020 at 3:45 AM wrote:
> Build failed.
>
> - kudu-build-test-arm64-in-docker
> https://logs.openlabtesting.org/logs/periodic-kudu-mail/github.com/apache/kudu/master/kudu-build-test-arm64-in-docker/361e52b/
> : FAILURE in 2h 43m 31s
>
rowse/KUDU-3170 tracks fixing this.
On Sat, Jul 18, 2020 at 3:49 AM wrote:
> Build failed.
>
> - kudu-build-test-arm64-in-docker
> https://logs.openlabtesting.org/logs/periodic-kudu-mail/github.com/apache/kudu/master/kudu-build-test-arm64-in-docker/20ae949/
> : FAILURE in 2h 46m 37
ac39/
> : FAILURE in 2h 45m 22s
>
--
Grant Henke
Software Engineer | Cloudera
gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
Hi Zhao,
I have added you as a contributor on Jira. Welcome to the Kudu community!
Thank you,
Grant
On Mon, Jun 8, 2020 at 6:58 AM 赵 仁海 wrote:
> Hi
> Could I become a contributor?
> My Apache Jira username: RenhaiZhao
>
>
> Thanks & Best Regards
> Zhao Renhai
>
k of the proposal.
Thank you,
Grant
--
Grant Henke
Software Engineer | Cloudera
gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
would also be
> appreciated.
> Also, it's worth running Kudu Java tests against kudu-binary JAR artifact
> as described in the commit message here:
>
>
> https://gitbox.apache.org/repos/asf?p=kudu.git;a=commit;h=8a6faaa93f3e206ac75e8087731daccaf7ab646a
>
> The vo
st and
> >>> efficient. One of the challenges here has been integration with Apache
> >>> Impala, and providing a common abstraction that can be used by both
> >>> codebases. This work is still ongoing but is drawing to a close pretty
> >>> soon.
> >>>
> >>> Please join me in congratulating Bankim!
> >>>
> >>
>
--
Grant Henke
Software Engineer | Cloudera
gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
I ran the following to test various OS versions in Docker:
*# Build all the images*
*export
BASES="centos:7,centos:8,ubuntu:xenial,ubuntu:bionic,debian:stretch"*
*export TARGETS="build"*
*./docker/docker-build.sh*
*# For each image, run the tests*
*docker run -it --rm apache/kudu:build-latest-
nice to cut out that surface area.
> >
> > -Todd
> >
> > On Mon, Apr 13, 2020 at 11:39 AM Bankim Bhavsar
> >
> > wrote:
> >
> > > LGTM.
> > >
> > > Bankim
> > >
> > > On Sun, Apr 12, 2020 at 10:48 AM Grant Hen
Hello Kudu Developers,
As we approach the 1.12.0 release I think now is a good opportunity to
evaluate the platform versions
we support. Doing so before the 1.12.0 release is useful because it will
allow us to mark any OS we
intend to drop as deprecated. This is similar to how we have handled
s./gradle
checkstyle# Just run Spotbugs checks./gradle spotbugs# Just assemble the
project with no checks or tests../gradlew assemble# Print out a list of
available tasks such as assemble, check, test, etc./gradlew tasks*
Let me know if you have any questions or concerns.
Thank you,
Grant
--
hanks a lot Grant for the proposal!
> >
> > Best,
> > Hao
> >
> > On Tue, Mar 10, 2020 at 9:00 AM Grant Henke >
> > wrote:
> >
> > > Hello Kudu developers,
> > >
> > > With a large majority of the Apache Ranger integration work landing,
/validating
it though.
Please let me know if you have any thoughts or feedback on the above plan.
Thank you,
Grant
On Tue, Aug 13, 2019 at 3:06 AM Adar Lieber-Dembo
wrote:
> +1, thanks for all of the details.
>
> On Fri, Aug 9, 2019 at 3:21 PM Grant Henke wrote:
> >
> >
hub.com/apache/kudu/blob/branch-1.11.x/docs/release_notes.adoc
> > > >
> > > > The KEYS file to verify the artifact signatures can be found here:
> > > > https://dist.apache.org/repos/dist/release/kudu/KEYS
> > > >
> > > > I'd suggest going through the README
; > > > >
> > > > > The KEYS file to verify the artifact signatures can be found here:
> > > > > https://dist.apache.org/repos/dist/release/kudu/KEYS
> > > > >
> > > > > I'd suggest going through the README and the release notes,
> building
> > > Kudu,
> > > > > and
> > > > > running the unit tests. Testing out the Maven repo would also be
> > > > > appreciated.
> > > > > Also, it's worth running Kudu Java tests against kudu-binary JAR
> > > artifact
> > > > > as described in the commit message here:
> > > > >
> > > > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=kudu.git;a=commit;h=8a6faaa93f3e206ac75e8087731daccaf7ab646a
> > > > >
> > > > > This vote runs until Tue Nov 19 15:00:00 PST 2019.
> > > > > That's over 72 hours from the time of sending out this e-mail
> message
> > > due
> > > > > to the weekend.
> > > > >
> > > > >
> > > > > Kind regads,
> > > > >
> > > > > Alexey
> > >
> >
> >
> > --
> > Andrew Wong
> >
>
--
Grant Henke
Software Engineer | Cloudera
gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
:54 PM Grant Henke wrote:
> I posted a patch to the Apache Flume project tracked here:
> https://issues.apache.org/jira/browse/FLUME-3345
>
> On Wed, Sep 18, 2019 at 2:08 PM Grant Henke wrote:
>
>> I think we should contribute the integration to Apache Flume first
>>
ou can see an example of this here:
> > > https://issues.apache.org/jira/browse/IMPALA-6478
> > >
> > > I think this is pretty useful and I’d get it enabled for Kudu too. Does
> > > anyone object? If I don’t hear any objections by next Wednesday I’ll go
> > > a
> announce only when Kudu 1.11.1 is out with KUDU-2990 addressed?
> > >
> > > Given the timing and the fact that Kudu 1.11.0 artifacts are already
> > > published, I think one of the possible paths forward is to proceed with
> > the
> > > announcement of Kudu 1.11.0 releas
I posted a patch to the Apache Flume project tracked here:
https://issues.apache.org/jira/browse/FLUME-3345
On Wed, Sep 18, 2019 at 2:08 PM Grant Henke wrote:
> I think we should contribute the integration to Apache Flume first
>
> before removing it from Kudu.
>
>
> I am
explicit deprecation), though
> I think we should contribute the integration to Apache Flume first
> before removing it from Kudu.
>
> On Wed, Sep 18, 2019 at 11:58 AM Grant Henke
> wrote:
> >
> > Hi Kudu Developers,
> >
> > Now that we have complete Java based test
Hello Kudu Users!
Please fill out the first Apache Kudu community survey and tell us how
you're using Kudu and how we can make it better.
https://forms.gle/5pRzhh38sZwZt69U7
The results of this survey will help drive community focus, direction, and
future blog content. It will also be used to
Hello Kudu devs!
The vote for Apache Kudu 1.10.0-RC3 has closed. It passes with:
5 binding +1s:
- Alexey Serbin
- Hao Hao
- Andrew Wong
- Yingchun Lai
- Grant Henke
0 -1s of any kind.
I will continue going through the release steps over the coming days.
--
Grant Henke
y working on it.
>
> Thanks,
> --
> *Ritwik Yadav*
>
--
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
CSB for a couple billion rows with various workloads against a
> > single node, performance looked pretty good.
> >
> > -Todd
> >
> > On Fri, Jun 21, 2019 at 7:35 PM Grant Henke >
> > wrote:
> >
> > > Hello Kudu devs!
> > >
> > > The
,
Grant
--
Grant Henke
Software Engineer | Cloudera
gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
Jun 14, 2019 at 5:20 PM Grant Henke wrote:
> Hello Kudu devs!
>
> The Apache Kudu team is happy to announce the first release candidate for
> Apache Kudu 1.10.0.
>
> Apache Kudu 1.10.0 is a minor release that offers many improvements and
> fixes since the prior release.
>
&
to the weekend.
Thank you,
Grant
--
Grant Henke
Software Engineer | Cloudera
gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
ranthenke/kudu>.
Let me know if you have any concerns.
Thank you,
Grant
--
Grant Henke
Software Engineer | Cloudera
gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
!) and put together an RC1
ASAP.
As always, if you have questions or concerns, don't hesitate to reach out.
Thanks,
Grant
On Tue, Jun 11, 2019 at 7:56 AM Grant Henke wrote:
> I am planning to branch tomorrow morning. Is there anything else pressing
> that needs to be done? If so, let m
Hi devs,
The restart is complete and Gerrit appears to have started up successfully.
Thanks,
Grant
On Wed, Jun 12, 2019 at 4:57 PM Grant Henke wrote:
> Hi devs,
>
> Kudu is branching and we need to update our Gerrit replication
> config to account for the new branch. There wil
Hi devs,
Kudu is branching and we need to update our Gerrit replication
config to account for the new branch. There will be a brief period downtime
that shouldn't last more than 10 minutes. If you have any concerns, don't
hesitate to reach out.
Thanks,
Grant
--
Grant Henke
Software Engineer
I am planning to branch tomorrow morning. Is there anything else pressing
that needs to be done? If so, let me know.
On Thu, Jun 6, 2019 at 3:32 PM Grant Henke wrote:
> We have time for release notes, they can be done early next week.
>
> On Thu, Jun 6, 2019 at 3:31 PM Mike Per
config files to make it easier to connect to
> multi-master
> > clusters
> >
> > Yingchun has also been contributing by helping new users on Slack, and
> > helps operate 6 production clusters at Xiaomi, one of our larger
> > installations in China.
> &
not be able to add release
> notes by tomorrow, might need a little more time for that.
>
> Mike
>
> On Thu, Jun 6, 2019 at 7:31 AM Grant Henke
> wrote:
>
> > I've created a Google doc to collect 1.10.0 release notes:
> >
> >
> https://docs.google.com/docume
-parent --author=
Please let me know if you agree with this plan, have comments, questions,
concerns, etc.
Thanks!
--
Grant Henke
Software Engineer | Cloudera
gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
cently with other tasks but getting back
> into Beam development again.
>
>
>
>
> On Tue, Mar 5, 2019 at 9:16 AM Mike Percy wrote:
>
> > Hi devs,
> > For the 1.9.0 release, we (Grant Henke, Brian McDevitt, and I)
> implemented
> > the capability to start a K
release notes, building
> Kudu,
> > and
> > running the unit tests. Testing out the Maven repo would also be
> > appreciated.
> >
> > The vote will run until this coming Friday, March 1st at 11:59AM PST.
> >
> >
> > Thank you,
> > Andrew
>
--
Grant Henke
Software Engineer | Cloudera
gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
e binaries in the form of a Maven repository are
> > staged here:
> > > > >
> > https://repository.apache.org/content/repositories/orgapachekudu-1028/
> > > > >
> > > > > It is tagged in Git as 1.9.0-RC1 and the corresponding hash is the
> > > > > following:
> > > > >
> >
> https://gitbox.apache.org/repos/asf?p=kudu.git;a=commit;h=76e8af74e151c018de7e3d6aa34fadd49bf41601
> > > > > <
> >
> https://git-wip-us.apache.org/repos/asf?p=kudu.git;a=commit;h=76e8af74e151c018de7e3d6aa34fadd49bf41601
> > >
> > > > >
> > > > > A draft of the release notes can be found here:
> > > > > https://gerrit.cloudera.org/c/12389/
> > > > >
> > > > > The KEYS file to verify the artifact signatures can be found here:
> > > > > https://dist.apache.org/repos/dist/release/kudu/KEYS
> > > > >
> > > > > I'd suggest going through the README and the release notes,
> building
> > Kudu, and running the unit tests. Testing out the Maven repo would also
> be
> > appreciated.
> > > > >
> > > > > The vote will run until Monday, February 25th at 11:59AM PST. This
> > is a bit over the suggested 72 hours due to the weekend.
> > > > >
> > > > >
> > > > > Thank you,
> > > > > Andrew
> > > > >
> >
>
--
Grant Henke
Software Engineer | Cloudera
gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
On Wed, Feb 6, 2019 at 12:00 PM Grant Henke wrote:
> I proactively opened INFRA-17817
> <https://issues.apache.org/jira/browse/INFRA-17817> to change this
> policy. Regardless of the route we take it's good to avoid any mistakes.
>
> On Wed, Feb 6, 2019 at 11:52 AM Grant
I proactively opened INFRA-17817
<https://issues.apache.org/jira/browse/INFRA-17817> to change this policy.
Regardless of the route we take it's good to avoid any mistakes.
On Wed, Feb 6, 2019 at 11:52 AM Grant Henke wrote:
> I found the Kafka Infra jira to use for reference shoul
I found the Kafka Infra jira to use for reference should we need it:
https://issues.apache.org/jira/browse/INFRA-16144
On Wed, Feb 6, 2019 at 11:50 AM Grant Henke wrote:
> It looks like the Kudu committer merging a patch has full control over the
> strategy currently:
> [image:
requires an INFRA jira to change.
[image: image.png]
On Wed, Feb 6, 2019 at 11:36 AM Brock Noland wrote:
> I assume if we used Github PR's we configure merges to occur without merge
> commits? I find them very confusing.
>
> On Wed, Feb 6, 2019 at 9:57 AM Grant Henke
> wrote:
&
hanges, labels, etc
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 En
- Ensure consensus on the move (a link to a lists.apache.org thread
> will
> > > > suffice for us as evidence).
> > > > - Create a JIRA ticket at
> https://issues.apache.org/jira/browse/INFRA
> > > >
> > > > Your migration should only take a few minutes. If
> >>> runtime with a JUnit test. Do you think we could cache the artifacts
> > >>> somewhere, maybe in the Maven repo somehow, so we don't have to
> > download
> > >>> the artifact every time we want to use it? I was hoping to simply be
> > able
> > &
ant!
>
> Mike
>
> On Thu, Oct 4, 2018 at 12:07 PM Dan Burkert wrote:
>
> > Sounds great, thanks for chasing this down!
> >
> > - Dan
> >
> > On Wed, Oct 3, 2018 at 7:20 PM Grant Henke
> > wrote:
> >
> > > Hi Kudu dev community,
> &g
to the
current version of the config file.
Please reach out if you have any concerns about this.
Thanks,
Grant
--
Grant Henke
Software Engineer | Cloudera
gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
d test
> retry to make the pre-commit change).
>
> On Fri, Apr 27, 2018 at 10:05 AM, Grant Henke wrote:
> > A recent patch has evaluated and addressed any remaining Artifact issues.
> > See the commit message here for details:
> >
> h
rch engines
>(SlackArchive.io has shut down)
>
> Please offer your suggestions for where we can get a good bang for our
> collective buck, and if there is anything you would like to work on by all
> means please either speak up or feel free to reach out directly.
>
> Thanks,
>
> Grant and Mike
>
>
--
Grant Henke
Software Engineer | Cloudera
gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
s shut down)
>>
>> Please offer your suggestions for where we can get a good bang for our
>> collective buck, and if there is anything you would like to work on by all
>> means please either speak up or feel free to reach out directly.
>>
>> Thanks,
>>
>> Grant and Mike
>>
>>
>
> --
> Mauricio Aristizabal
> Architect - Data Pipeline
> mauri...@impact.com | 323 309 4260
> https://impact.com
><https://www.facebook.com/ImpactMarTech/>
> <https://twitter.com/impactmartech>
>
>
--
Grant Henke
Software Engineer | Cloudera
gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
The Apache Kudu team is happy to announce the release of Kudu 1.7.1.
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
; > > > and all tests pass. I cherry-picked this commit on branch-1.7.x
> in
> > > case
> > > > > > there will be a 1.7.2 or a 1.7.1-RC3.
> > > > > > * Java build on MacOS succeeds, all tests passed.
> > > > > > * Tested
sure about the
> policy on the release notes though.
>
> Thanks for this RC, Grant!
>
> Attila
>
>
> > On 2018. May 30., at 15:44, Grant Henke wrote:
> >
> > Hi,
> >
> > The Apache Kudu team is happy to announce the first release candidate for
>
nk you,
Grant
--
Grant Henke
Software Engineer | Cloudera
gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
an issue that should block the release (I
>
> hope to have some time to a look at the breakages soon).
>
>
> Thank you very much for taking care of the release management for
>
> 1.7.1,
>
> Grant!
>
>
>
>
> Kind regards,
>
> Alexey
>
>
>
&
sing Gradle in place of Maven
5. Remove the Maven build from the project
- This shouldn't be immediately but maintaining 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
--
G
so that retried flaky tests don't fail build-and-test.sh
> by leaving behind test directories.
>
>
> On Thu, Apr 26, 2018 at 3:01 PM, Grant Henke <ghe...@cloudera.com> wrote:
> > Hi Kudu dev community,
> >
> > Since Kudu 1.7.0 was released a few important fixes hav
://kudu.apache.org/releases/1.7.0/
Full release notes:
https://kudu.apache.org/releases/1.7.0/docs/release_notes.html
Regards,
The Apache Kudu team
--
Grant Henke
Software Engineer | Cloudera
gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
Thanks very much to everyone who voted! A +1 from me as well.
The vote to release 1.7.0 RC2 is now closed. Here are the results:
8 binding +1 votes
1 non-binding +1 vote
no -1 votes
The vote passes and 1.7.0 RC2 will become the official 1.7.0 release.
I will prepare the artifacts and send out
qweKUACgkQXkPKua7Hfq+7DQCg4t6llqevULFCmEIzGHrh7YSv
> nXoAoPvJUrYpP46KC1TQP/exD57qS3TO
> =+kkn
> -END PGP SIGNATURE-
>
>
>
> On Fri, Mar 16, 2018 at 6:28 PM, Grant Henke <ghe...@cloudera.com> wrote:
>
> > Hi,
> >
> > The Apache Kudu team is happ
4 days instead.
Thank you,
Grant
--
Grant Henke
Software Engineer | Cloudera
gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
gt; On Fri, Mar 16, 2018 at 12:42 PM, Grant Henke <ghe...@cloudera.com> wrote:
> > Hi,
> >
> > The Apache Kudu team is happy to announce the first release candidate for
> > Apache Kudu 1.7.0.
> >
> > Apache Kudu 1.7.0 is a minor release that offers many impro
minute, such as release notes or bug
fixes.
Thank you,
Grant
On Thu, Mar 8, 2018 at 12:18 PM, Grant Henke <ghe...@cloudera.com> wrote:
> Hi Kudu dev community,
>
> Apologies for the delay on this release. Given I missed the initial
> branching target date
> I would like to propose
as possible.
Thank you,
Grant
On Thu, Feb 22, 2018 at 4:09 PM, Mike Percy <mpe...@apache.org> wrote:
> Belated +1 Grant, thanks for volunteering to handle the release!
>
> Mike
>
> On Thu, Feb 15, 2018 at 2:42 PM, Grant Henke <ghe...@cloudera.com> wrote:
>
> >
know your thoughts on the above plan.
Thanks,
Grant
--
Grant Henke
Software Engineer | Cloudera
gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
cimal
precisions 39 to 77 with internal INT256 support (or VarInt).
On Mon, Nov 20, 2017 at 6:51 PM, Todd Lipcon <t...@cloudera.com> wrote:
> On Mon, Nov 20, 2017 at 1:12 PM, Grant Henke <ghe...@cloudera.com> wrote:
>
> > Thank you for the feedback. Below are some respon
n SQL, but no such precedent for int128.
>>
>>
>> 2) Encoders: like Dan mentioned, it seems like we might not be able to do
>> a
>> very efficient job of encoding these very large integers. Stuff like
>> bitshuffle, SIMD bitpacking, etc, isn't really designed for suc
you,
Grant
--
Grant Henke
Software Engineer | Cloudera
gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke
;
> > > I propose we branch 1.5 this coming Monday, August 28th, with the aim
> to
> > > start a vote on Wednesday, August 30th or the following day.
> > >
> > > If you have authored any major improvements since 1.4, now is the time
> to
> > > start
, (2)
> > > issue a
> > > > > new minor release with the deprecation in place. Before you
> > completely
> > > > > remove the functionality in a new major release there should be at
> > > least
> > > > > one minor rele
88 matches
Mail list logo
