Re: [LICENSE QUESTION] Use jmh as a benchmark tool

[Julian Hyde]

PS Use of jmh was addressed explicitly:
https://issues.apache.org/jira/browse/LEGAL-399

On Fri, Dec 29, 2023 at 4:50 PM Julian Hyde  wrote:
>
> According to https://issues.apache.org/jira/browse/LEGAL-450, it's OK
> to use a GPL linter. And a project can use GPL "build tools provided
> they leave no code traces (licensed under a cat X license) in your
> final release artifacts".
>
> In Calcite we use jmh on the understanding that it does not produce
> any artifacts and therefore was acceptable.
>
> Can someone explain how a benchmarking utility is different from a linter?
>
> Julian
>
> On Wed, Dec 27, 2023 at 9:19 AM tison  wrote:
> >
> > > For instance, if your maven build is `-Pbenchmark` and it's clear
> > > that the user needs to include this license when compiling from source.
> >
> > Yeah. I'm going to collaborate with Fury to follow this approach and
> > document clearly how a developer can intentionally run benchmark with
> > JMH as a dep.
> >
> > Best,
> > tison.
> >
> > John D. Ament  于2023年12月28日周四 01:07写道：
> > >
> > > On Wed, Dec 27, 2023 at 11:38 AM tison  wrote:
> > >
> > > > > application, a developer has preinstalled the JDK (or using a manager 
> > > > > of
> > > > > some kind to install it - so not something we're forcing upon them).  
> > > > > In
> > > >
> > > > No. To running a Java Application in a normal way, the JRE is
> > > > required. Saying "not something we're forcing upon them" sounds
> > > > sophistry.
> > > >
> > > > Best,
> > > > tison.
> > > >
> > > > tison  于2023年12月28日周四 00:27写道：
> > > > >
> > > > > Hi John,
> > > > >
> > > > > Glad to hear your feedback. Reply inline:
> > > > >
> > > > > > In the case of JMH, the repository I linked above forces the user to
> > > > download
> > > > > > the additional dependency from maven central (or similar repository)
> > > > rather
> > > > > > than relying on the system preinstalled library.
> > > > >
> > > > > From a technical view, this is not true because you can download the
> > > > > libs manually and place them under MAVEN_HOME. Then it can be regarded
> > > > > as a "system preinstalled library". It's the same as download JDK and
> > > > > place them under JAVA_HOME.
> > > >
> > >
> > > Except that's not how these libraries are listed within your pom file.  If
> > > there was a step where you required a developer to download these files,
> > > what you're describing would be accurate, but they're downloaded in an
> > > automated fashion.  Keep in mind, this isn't the JMH that's distributed
> > > with the JDK that you're using here, it's an add-on library you're using.
> > >
> > >
> > > > >
> > > > > > you can't use org.openjdk.jmh:* as a compile/test compile
> > > > > > dependency in your project
> > > > >
> > > > > fury-benchmark is not released in binary form. But we can of course
> > > > > make it an optional dependency (or the entire module optionally)
> > > > > behind a profile and deactivated by default so that it's the same as
> > > > > how ASF projects can optionally depend on MySQL Connector Java under
> > > > > the same license.
> > > >
> > >
> > > The question here isn't about binary form.  Keep in mind that first and
> > > foremost ASF projects produce source code releases, the convenience
> > > binaries are a separate artifact.  I'm presently approaching your thread
> > > focused on the source code release.  I can see your point though and 
> > > that's
> > > where I'm suggesting asking legal may give you additional guidance that I
> > > could see leading to a similar situation as Java 9 JavaScript embeddings.
> > > Just keep in mind that you're making a module optional to compile, rather
> > > than optional to use, even though it's only being used for testing 
> > > purposes
> > > and our expectation (even though it may differ from reality) is that we're
> > > reviewing the contents of the source bundle that a user downloads to
> > > compile your code, not the binary artifact they depend upon in their
> > > projects.
> > >
> > >
> > > > >
> > > > > A related discussion can be found at [1].
> > > >
> > >
> > > Yes, and Hen's response is very appropriate to that situation.  It's not
> > > really relevant to your situation though since the concern in this thread
> > > is your source release, not binary release.  You can make something like
> > > this optional, and if you keep the benchmark as optional you should be 
> > > fine
> > > as well.  For instance, if your maven build is `-Pbenchmark` and it's 
> > > clear
> > > that the user needs to include this license when compiling from source.
> > >
> > >
> > > > >
> > > > > >> THEY MAY BE RELIED UPON WHEN THEY SUPPORT AN OPTIONAL FEATURE
> > > > > >> "Will the majority of users want to use my product without adding 
> > > > > >> the
> > > > optional components?"
> > > > >
> > > > > No. Benchmark is for testing; most users don't even know it and cannot
> > > > > depend on it as a Maven artifact.
> > >
> > > >
> > > > > P.S.
> > > > > > don't approach things as "TLP 

Re: [LICENSE QUESTION] Use jmh as a benchmark tool

[Julian Hyde]

According to https://issues.apache.org/jira/browse/LEGAL-450, it's OK
to use a GPL linter. And a project can use GPL "build tools provided
they leave no code traces (licensed under a cat X license) in your
final release artifacts".

In Calcite we use jmh on the understanding that it does not produce
any artifacts and therefore was acceptable.

Can someone explain how a benchmarking utility is different from a linter?

Julian

On Wed, Dec 27, 2023 at 9:19 AM tison  wrote:
>
> > For instance, if your maven build is `-Pbenchmark` and it's clear
> > that the user needs to include this license when compiling from source.
>
> Yeah. I'm going to collaborate with Fury to follow this approach and
> document clearly how a developer can intentionally run benchmark with
> JMH as a dep.
>
> Best,
> tison.
>
> John D. Ament  于2023年12月28日周四 01:07写道：
> >
> > On Wed, Dec 27, 2023 at 11:38 AM tison  wrote:
> >
> > > > application, a developer has preinstalled the JDK (or using a manager of
> > > > some kind to install it - so not something we're forcing upon them).  In
> > >
> > > No. To running a Java Application in a normal way, the JRE is
> > > required. Saying "not something we're forcing upon them" sounds
> > > sophistry.
> > >
> > > Best,
> > > tison.
> > >
> > > tison  于2023年12月28日周四 00:27写道：
> > > >
> > > > Hi John,
> > > >
> > > > Glad to hear your feedback. Reply inline:
> > > >
> > > > > In the case of JMH, the repository I linked above forces the user to
> > > download
> > > > > the additional dependency from maven central (or similar repository)
> > > rather
> > > > > than relying on the system preinstalled library.
> > > >
> > > > From a technical view, this is not true because you can download the
> > > > libs manually and place them under MAVEN_HOME. Then it can be regarded
> > > > as a "system preinstalled library". It's the same as download JDK and
> > > > place them under JAVA_HOME.
> > >
> >
> > Except that's not how these libraries are listed within your pom file.  If
> > there was a step where you required a developer to download these files,
> > what you're describing would be accurate, but they're downloaded in an
> > automated fashion.  Keep in mind, this isn't the JMH that's distributed
> > with the JDK that you're using here, it's an add-on library you're using.
> >
> >
> > > >
> > > > > you can't use org.openjdk.jmh:* as a compile/test compile
> > > > > dependency in your project
> > > >
> > > > fury-benchmark is not released in binary form. But we can of course
> > > > make it an optional dependency (or the entire module optionally)
> > > > behind a profile and deactivated by default so that it's the same as
> > > > how ASF projects can optionally depend on MySQL Connector Java under
> > > > the same license.
> > >
> >
> > The question here isn't about binary form.  Keep in mind that first and
> > foremost ASF projects produce source code releases, the convenience
> > binaries are a separate artifact.  I'm presently approaching your thread
> > focused on the source code release.  I can see your point though and that's
> > where I'm suggesting asking legal may give you additional guidance that I
> > could see leading to a similar situation as Java 9 JavaScript embeddings.
> > Just keep in mind that you're making a module optional to compile, rather
> > than optional to use, even though it's only being used for testing purposes
> > and our expectation (even though it may differ from reality) is that we're
> > reviewing the contents of the source bundle that a user downloads to
> > compile your code, not the binary artifact they depend upon in their
> > projects.
> >
> >
> > > >
> > > > A related discussion can be found at [1].
> > >
> >
> > Yes, and Hen's response is very appropriate to that situation.  It's not
> > really relevant to your situation though since the concern in this thread
> > is your source release, not binary release.  You can make something like
> > this optional, and if you keep the benchmark as optional you should be fine
> > as well.  For instance, if your maven build is `-Pbenchmark` and it's clear
> > that the user needs to include this license when compiling from source.
> >
> >
> > > >
> > > > >> THEY MAY BE RELIED UPON WHEN THEY SUPPORT AN OPTIONAL FEATURE
> > > > >> "Will the majority of users want to use my product without adding the
> > > optional components?"
> > > >
> > > > No. Benchmark is for testing; most users don't even know it and cannot
> > > > depend on it as a Maven artifact.
> >
> > >
> > > > P.S.
> > > > > don't approach things as "TLP [x] does it this way so
> > > > > it must be the preferred way"
> > > > Yeah .. Even I don't think Flink did it correctly, this expression
> > > > increases confusion. Most readers don't have the context to understand
> > > > the referred case. I'll avoid it.
> > > >
> > > > Best,
> > > > tison.
> > > >
> > > > [1] https://issues.apache.org/jira/browse/LEGAL-437
> > > >
> > > > John D. Ament  于2023年12月27日周三 23:57写道：
> > > 

Re: [DISCUSS] Gluten proposal

[Rakesh Radhakrishnan]

+1

Thank you Shaofeng for the details.

I've connected with my colleagues at Microsoft and the project roadmap is
super exciting to me. As my colleagues are part of various Apache projects
Spark, Hadoop, Flink, Trino projects, I believe I can provide insights and
add diversity to this project.

Happy to be a mentor on this proposal during the incubation process, if you
are interested.

Thanks,
Rakesh

On Thu, Dec 28, 2023 at 6:47 AM ShaoFeng Shi  wrote:

> Hi Rakesh,
>
> Yeah, the team aware that, they plan to merge the Trino plugin into the
> main repository at some point of time, depends on its maturity. The Hive
> plugin is not on current roadmap I think, but this is open for discussion.
>
> Best regards,
>
> Shaofeng Shi 史少锋
> Apache Kylin PMC,
> Apache Incubator PMC,
> Email: shaofeng...@apache.org
>
> Apache Kylin FAQ: https://kylin.apache.org/docs/gettingstarted/faq.html
> Join Kylin user mail group: user-subscr...@kylin.apache.org
> Join Kylin dev mail group: dev-subscr...@kylin.apache.org
>
>
>
>
> Rakesh Radhakrishnan  于2023年12月27日周三 14:06写道：
>
> > OK, that's really interesting. I hope you will add  "Gluten-Trino
> > " and "Gluten-Flink" as
> > sub-projects(plugin module) under the main Gluten project and follow a
> > single release cycle?
> >
> > Is it technically/architecturally feasible to develop a "Gluten-Hive"
> > plugin (as we know Hive uses Apache Tez DAG) as a long term plan ?
> >
> > Thanks,
> > Rakesh
> >
> > On Tue, Dec 26, 2023 at 4:30 PM ShaoFeng Shi 
> > wrote:
> >
> > > Hi Rakesh,
> > >
> > > Thanks for your comment. The Trino plugin is under PoC, not ready for
> > > widely use at this moment, so it is staged in another git repository:
> > > https://github.com/oap-project/Gluten-Trino
> > > Flink support is still in early discussion stage, need more
> collaboration
> > > in the future.
> > >
> > > Best regards,
> > >
> > > Shaofeng Shi 史少锋
> > > Apache Kylin PMC,
> > > Apache Incubator PMC,
> > > Email: shaofeng...@apache.org
> > >
> > > Apache Kylin FAQ:
> https://kylin.apache.org/docs/gettingstarted/faq.html
> > > Join Kylin user mail group: user-subscr...@kylin.apache.org
> > > Join Kylin dev mail group: dev-subscr...@kylin.apache.org
> > >
> > >
> > >
> > >
> > > Rakesh Radhakrishnan  于2023年12月26日周二 11:24写道：
> > >
> > > > Thanks Shaofeng and team for the efforts!
> > > >
> > > > Its really interesting to see that Flink and Trino projects can get
> the
> > > > benefits of Gluten and boost their performance. Much appreciated, if
> > you
> > > > could share more on this integration, perf_numbers,
> > > pullrequest_reference,
> > > > jira_reference etc. Will Flink and Trino already have a plugin
> > mechanism
> > > in
> > > > place to seamlessly integrate with Gluten ?
> > > >
> > > > Thanks,
> > > > Rakesh
> > > >
> > > > On Sat, Dec 23, 2023 at 6:13 PM ShaoFeng Shi  >
> > > > wrote:
> > > >
> > > > > Hi Enrico,
> > > > >
> > > > > This is a good question. Actually I asked the same to the team when
> > > they
> > > > > find me for coaching.
> > > > >
> > > > > As the proposal mentioned, Gluten is a middle layer between the
> > > JVM-based
> > > > > SQL engine and native libraries. It connects the two sides, and
> build
> > > > > common services like unified plan transformation, seamless native
> > > > > integration, clear JNI interfaces, etc. Spark is the first engine
> it
> > > > > supports now, but the framework and mechanism can also work for
> other
> > > > > engines like Trino, Flink SQL in the future (the proposal also
> > > mentioned
> > > > > this). Underlying Gluten, it can integrate with different
> libararies,
> > > > like
> > > > > Velox, Clickhouse and Arrow (not ready yet). So, its mission and
> > scope
> > > is
> > > > > different, that's why we put it as a new project.
> > > > >
> > > > > Best regards,
> > > > >
> > > > > Shaofeng Shi 史少锋
> > > > > Apache Kylin PMC,
> > > > > Apache Incubator PMC,
> > > > > Email: shaofeng...@apache.org
> > > > >
> > > > > Apache Kylin FAQ:
> > > https://kylin.apache.org/docs/gettingstarted/faq.html
> > > > > Join Kylin user mail group: user-subscr...@kylin.apache.org
> > > > > Join Kylin dev mail group: dev-subscr...@kylin.apache.org
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Enrico Olivelli  于2023年12月22日周五 22:43写道：
> > > > >
> > > > > > Shaofeng,
> > > > > >
> > > > > > Il giorno ven 22 dic 2023 alle ore 13:59 ShaoFeng Shi
> > > > > >  ha scritto:
> > > > > > >
> > > > > > > Hi IPMC members,
> > > > > > >
> > > > > > > I would like to propose a new project to the ASF incubator -
> > > Gluten.
> > > > > > >
> > > > > > > Gluten[1] is a middle layer responsible for offloading Apache
> > Spark
> > > > SQL
> > > > > > > queries to native engines. This project aims to address the CPU
> > > > > > > computational bottleneck to offload SparkSQL operators to
> native
> > > > > engines
> > > > > > in
> > > > > > > data loading scenarios based on Apache Spark.
> > > > > >
> > > > > > 

Re: [VOTE] Release Apache OpenDAL(incubating) 0.44.0-rc.1 - Incubator Vote Round 1

[tison]

+1 (binding)

Thank you Xuanwo. I use macos Finder's extract UI and it fails to
build. Using `tar -xvf` works.

Best,
tison.

Xuanwo  于2023年12月29日周五 22:00写道：
>
> Hi, tison
>
> The tarball doesn't have `bindings/c` in the `Cargo.toml`
>
> ```toml
>   18   │ [workspace]
>   19   │ default-members = ["core"]
>   20   │ exclude = [
>   21   │ "examples",
>   22   │
>   23   │ ]
>   24   │ members = [
>   25   │   "core",
>   26   │   "core/fuzz",
>   27   │   "core/edge/*",
>   28   │   "core/benches/vs_*",
>   29   │
>   30   │   "bindings/nodejs",
>   31   │   "bindings/python",
>   32   │   "bindings/java",
>   33   │
>   34   │
>   35   │ ]
>   36   │ resolver = "2"
> ```
>
> We used to met dirty cache issues on other platforms. Would you like to 
> double check it?
>
> Use `tar -xvf` to extract the tarball instead of using a system decompression 
> application.
>
> On Fri, Dec 29, 2023, at 16:30, tison wrote:
> > -1 binding
> >
> > + Download links valid
> > + GPG sign correctly
> >
> > $ for i in (*.tgz|*.tar.gz|*.nupkg); do echo $i; gpg --verify $i.asc $i; 
> > done
> > apache-opendal-incubating-0.44.0-src.tar.gz
> > gpg: Signature made 二 12/26 20:49:34 2023 CST
> > gpg:using RSA key 25812FA45EC6D2DDCBE4B6604F43CB2BC2E9EFE5
> > gpg: Good signature from "dqhl76 (Identifier for authoring code on
> > GitHub) " [unknown]
> > gpg: aka "Liuqing Yue (Apache Committer)
> > " [unknown]
> > gpg: WARNING: This key is not certified with a trusted signature!
> > gpg:  There is no indication that the signature belongs to the 
> > owner.
> > Primary key fingerprint: 2581 2FA4 5EC6 D2DD CBE4  B660 4F43 CB2B C2E9 EFE5
> >
> > + Checksum matched
> > + LICENSE and NOTICE exists
> >
> > - Cannot build and test Java binding:
> >
> > Caused by:
> >   failed to read
> > `/Users/tison/Labs/vropendal/apache-opendal-incubating-0.44.0-src/bindings/c/Cargo.toml`
> >
> > Caused by:
> >   No such file or directory (os error 2)
> >
> > Seems we exclude those directories and it cause build failure.
> >
> > Best,
> > tison.
> >
> > Xuanwo  于2023年12月28日周四 13:14写道：
> >>
> >> Carry my non-binding +1 VOTE from the dev@o.a.o
> >>
> >> On Thu, Dec 28, 2023, at 13:12, Liuqing Yue wrote:
> >> > Hello Incubator PMC,
> >> >
> >> > The Apache OpenDAL community has voted and approved the release of Apache
> >> > OpenDAL(incubating) 0.44.0-rc.1. We now kindly request the IPMC members
> >> > review and vote for this release.
> >> >
> >> > OpenDAL is a data access layer that allows users to easily and 
> >> > efficiently
> >> > retrieve data from various storage services in a unified way.
> >> >
> >> > OpenDAL community vote thread:
> >> >
> >> > https://lists.apache.org/thread/nycyfc1m6819bj8vsb20vmbnlhs0kbdn
> >> >
> >> > Vote result thread:
> >> >
> >> > https://lists.apache.org/thread/pfnlmn9vqn1rqdy54wzm3mkx1wnt9mv6
> >> >
> >> > The release candidate:
> >> >
> >> > https://dist.apache.org/repos/dist/dev/incubator/opendal/0.44.0-rc.1/
> >> >
> >> > This release has been signed with a PGP available here:
> >> >
> >> > https://downloads.apache.org/incubator/opendal/KEYS
> >> >
> >> > Git tag for the release:
> >> >
> >> > https://github.com/apache/incubator-opendal/releases/tag/v0.44.0-rc.1
> >> >
> >> > Maven staging repo:
> >> >
> >> > https://repository.apache.org/content/repositories/orgapacheopendal-1022/
> >> >
> >> > Please download, verify, and test.
> >> >
> >> > The VOTE will be open for at least 72 hours and until the necessary
> >> > number of votes are reached.
> >> >
> >> > [ ] +1 approve
> >> > [ ] +0 no opinion
> >> > [ ] -1 disapprove with the reason
> >> >
> >> > To learn more about apache opendal, please see 
> >> > https://opendal.apache.org/
> >> >
> >> > Checklist for reference:
> >> >
> >> > [ ] Download links are valid.
> >> > [ ] Checksums and signatures.
> >> > [ ] LICENSE/NOTICE files exist
> >> > [ ] No unexpected binary files
> >> > [ ] All source files have ASF headers
> >> > [ ] Can compile from source
> >> >
> >> > More detailed checklist please refer to:
> >> > https://github.com/apache/incubator-opendal/tree/main/scripts
> >> >
> >> > To compile from source, please refer to:
> >> > https://github.com/apache/incubator-opendal/blob/main/CONTRIBUTING.md
> >> >
> >> > Here is python script in release to help you verify the release 
> >> > candidate:
> >> >
> >> > ./scripts/verify.py
> >> >
> >> > Thanks
> >> >
> >> > Liuqing Yue
> >> >
> >> > -
> >> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> > For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >> --
> >> Xuanwo
> >>
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >
> > 

Re: [VOTE] Release Apache OpenDAL(incubating) 0.44.0-rc.1 - Incubator Vote Round 1

[Xuanwo]

Hi, tison

The tarball doesn't have `bindings/c` in the `Cargo.toml`

```toml
  18   │ [workspace]
  19   │ default-members = ["core"]
  20   │ exclude = [
  21   │ "examples",
  22   │
  23   │ ]
  24   │ members = [
  25   │   "core",
  26   │   "core/fuzz",
  27   │   "core/edge/*",
  28   │   "core/benches/vs_*",
  29   │
  30   │   "bindings/nodejs",
  31   │   "bindings/python",
  32   │   "bindings/java",
  33   │
  34   │
  35   │ ]
  36   │ resolver = "2"
```

We used to met dirty cache issues on other platforms. Would you like to double 
check it?

Use `tar -xvf` to extract the tarball instead of using a system decompression 
application.

On Fri, Dec 29, 2023, at 16:30, tison wrote:
> -1 binding
>
> + Download links valid
> + GPG sign correctly
>
> $ for i in (*.tgz|*.tar.gz|*.nupkg); do echo $i; gpg --verify $i.asc $i; done
> apache-opendal-incubating-0.44.0-src.tar.gz
> gpg: Signature made 二 12/26 20:49:34 2023 CST
> gpg:using RSA key 25812FA45EC6D2DDCBE4B6604F43CB2BC2E9EFE5
> gpg: Good signature from "dqhl76 (Identifier for authoring code on
> GitHub) " [unknown]
> gpg: aka "Liuqing Yue (Apache Committer)
> " [unknown]
> gpg: WARNING: This key is not certified with a trusted signature!
> gpg:  There is no indication that the signature belongs to the owner.
> Primary key fingerprint: 2581 2FA4 5EC6 D2DD CBE4  B660 4F43 CB2B C2E9 EFE5
>
> + Checksum matched
> + LICENSE and NOTICE exists
>
> - Cannot build and test Java binding:
>
> Caused by:
>   failed to read
> `/Users/tison/Labs/vropendal/apache-opendal-incubating-0.44.0-src/bindings/c/Cargo.toml`
>
> Caused by:
>   No such file or directory (os error 2)
>
> Seems we exclude those directories and it cause build failure.
>
> Best,
> tison.
>
> Xuanwo  于2023年12月28日周四 13:14写道：
>>
>> Carry my non-binding +1 VOTE from the dev@o.a.o
>>
>> On Thu, Dec 28, 2023, at 13:12, Liuqing Yue wrote:
>> > Hello Incubator PMC,
>> >
>> > The Apache OpenDAL community has voted and approved the release of Apache
>> > OpenDAL(incubating) 0.44.0-rc.1. We now kindly request the IPMC members
>> > review and vote for this release.
>> >
>> > OpenDAL is a data access layer that allows users to easily and efficiently
>> > retrieve data from various storage services in a unified way.
>> >
>> > OpenDAL community vote thread:
>> >
>> > https://lists.apache.org/thread/nycyfc1m6819bj8vsb20vmbnlhs0kbdn
>> >
>> > Vote result thread:
>> >
>> > https://lists.apache.org/thread/pfnlmn9vqn1rqdy54wzm3mkx1wnt9mv6
>> >
>> > The release candidate:
>> >
>> > https://dist.apache.org/repos/dist/dev/incubator/opendal/0.44.0-rc.1/
>> >
>> > This release has been signed with a PGP available here:
>> >
>> > https://downloads.apache.org/incubator/opendal/KEYS
>> >
>> > Git tag for the release:
>> >
>> > https://github.com/apache/incubator-opendal/releases/tag/v0.44.0-rc.1
>> >
>> > Maven staging repo:
>> >
>> > https://repository.apache.org/content/repositories/orgapacheopendal-1022/
>> >
>> > Please download, verify, and test.
>> >
>> > The VOTE will be open for at least 72 hours and until the necessary
>> > number of votes are reached.
>> >
>> > [ ] +1 approve
>> > [ ] +0 no opinion
>> > [ ] -1 disapprove with the reason
>> >
>> > To learn more about apache opendal, please see https://opendal.apache.org/
>> >
>> > Checklist for reference:
>> >
>> > [ ] Download links are valid.
>> > [ ] Checksums and signatures.
>> > [ ] LICENSE/NOTICE files exist
>> > [ ] No unexpected binary files
>> > [ ] All source files have ASF headers
>> > [ ] Can compile from source
>> >
>> > More detailed checklist please refer to:
>> > https://github.com/apache/incubator-opendal/tree/main/scripts
>> >
>> > To compile from source, please refer to:
>> > https://github.com/apache/incubator-opendal/blob/main/CONTRIBUTING.md
>> >
>> > Here is python script in release to help you verify the release candidate:
>> >
>> > ./scripts/verify.py
>> >
>> > Thanks
>> >
>> > Liuqing Yue
>> >
>> > -
>> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> > For additional commands, e-mail: general-h...@incubator.apache.org
>>
>> --
>> Xuanwo
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org

-- 
Xuanwo

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Gluten proposal

[Yu Li]

+1, and I'm glad to be one of the nominated mentors.

My team members at Alibaba deeply joined in the development of Gluten and
Gluten-Trino, so I'm well aware that it's a diverse and open community, and
really glad that the Gluten community decides to join the incubator.

AFAIK, with Gluten-Trino plugin we could have some 50%~100% performance
gain, and I believe it could further improve after joining the Gluten main
branch later (not yet since that requires quite some code refactor, if I
understand it correctly, but that's in the plan).

About Flink plugin, I'm thrilled to see how things will develop, with my
Flink PMC Member hat on (smile).

Good luck team, and Happy New Year all!

Best Regards,
Yu


On Thu, 28 Dec 2023 at 12:34, Kent Yao  wrote:

> +1
>
> We have been using Glutin with Apache Kyuubi and Apache Spark
> at NetEase for about a year now. It's a promising project.
>
> And I'm glad to be one of the nominated mentors.
>
> Thanks,
> Kent Yao
>
> On 2023/12/28 03:25:56 ShaoFeng Shi wrote:
> > Hi Justin,
> >
> > Yeah, 12 months is a little tough; I have discussed this with the team,
> and
> > updated the proposal to 18 months.
> >
> > Best regards,
> >
> > Shaofeng Shi 史少锋
> > Apache Kylin PMC,
> > Apache Incubator PMC,
> > Email: shaofeng...@apache.org
> >
> > Apache Kylin FAQ: https://kylin.apache.org/docs/gettingstarted/faq.html
> > Join Kylin user mail group: user-subscr...@kylin.apache.org
> > Join Kylin dev mail group: dev-subscr...@kylin.apache.org
> >
> >
> >
> >
> > Justin Mclean  于2023年12月27日周三 13:53写道：
> >
> > > Hi,
> > >
> > > Looks like a good proposal. Only one thing stood out to me, while not
> > > impossible, planning to graduate in a year might not be easily
> achievable.
> > >
> > > Kind Regards,
> > > Justn
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache OpenDAL(incubating) 0.44.0-rc.1 - Incubator Vote Round 1

[tison]

-1 binding

+ Download links valid
+ GPG sign correctly

$ for i in (*.tgz|*.tar.gz|*.nupkg); do echo $i; gpg --verify $i.asc $i; done
apache-opendal-incubating-0.44.0-src.tar.gz
gpg: Signature made 二 12/26 20:49:34 2023 CST
gpg:using RSA key 25812FA45EC6D2DDCBE4B6604F43CB2BC2E9EFE5
gpg: Good signature from "dqhl76 (Identifier for authoring code on
GitHub) " [unknown]
gpg: aka "Liuqing Yue (Apache Committer)
" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:  There is no indication that the signature belongs to the owner.
Primary key fingerprint: 2581 2FA4 5EC6 D2DD CBE4  B660 4F43 CB2B C2E9 EFE5

+ Checksum matched
+ LICENSE and NOTICE exists

- Cannot build and test Java binding:

Caused by:
  failed to read
`/Users/tison/Labs/vropendal/apache-opendal-incubating-0.44.0-src/bindings/c/Cargo.toml`

Caused by:
  No such file or directory (os error 2)

Seems we exclude those directories and it cause build failure.

Best,
tison.

Xuanwo  于2023年12月28日周四 13:14写道：
>
> Carry my non-binding +1 VOTE from the dev@o.a.o
>
> On Thu, Dec 28, 2023, at 13:12, Liuqing Yue wrote:
> > Hello Incubator PMC,
> >
> > The Apache OpenDAL community has voted and approved the release of Apache
> > OpenDAL(incubating) 0.44.0-rc.1. We now kindly request the IPMC members
> > review and vote for this release.
> >
> > OpenDAL is a data access layer that allows users to easily and efficiently
> > retrieve data from various storage services in a unified way.
> >
> > OpenDAL community vote thread:
> >
> > https://lists.apache.org/thread/nycyfc1m6819bj8vsb20vmbnlhs0kbdn
> >
> > Vote result thread:
> >
> > https://lists.apache.org/thread/pfnlmn9vqn1rqdy54wzm3mkx1wnt9mv6
> >
> > The release candidate:
> >
> > https://dist.apache.org/repos/dist/dev/incubator/opendal/0.44.0-rc.1/
> >
> > This release has been signed with a PGP available here:
> >
> > https://downloads.apache.org/incubator/opendal/KEYS
> >
> > Git tag for the release:
> >
> > https://github.com/apache/incubator-opendal/releases/tag/v0.44.0-rc.1
> >
> > Maven staging repo:
> >
> > https://repository.apache.org/content/repositories/orgapacheopendal-1022/
> >
> > Please download, verify, and test.
> >
> > The VOTE will be open for at least 72 hours and until the necessary
> > number of votes are reached.
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > To learn more about apache opendal, please see https://opendal.apache.org/
> >
> > Checklist for reference:
> >
> > [ ] Download links are valid.
> > [ ] Checksums and signatures.
> > [ ] LICENSE/NOTICE files exist
> > [ ] No unexpected binary files
> > [ ] All source files have ASF headers
> > [ ] Can compile from source
> >
> > More detailed checklist please refer to:
> > https://github.com/apache/incubator-opendal/tree/main/scripts
> >
> > To compile from source, please refer to:
> > https://github.com/apache/incubator-opendal/blob/main/CONTRIBUTING.md
> >
> > Here is python script in release to help you verify the release candidate:
> >
> > ./scripts/verify.py
> >
> > Thanks
> >
> > Liuqing Yue
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
>
> --
> Xuanwo
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Graduate Apache OpenDAL (incubating) as a TLP - Incubator

[任春韶]

+1 non-binding

Best,
Chunshao Ren

Liuqing Yue  于2023年12月29日周五 15:28写道：

> +1 non-binding
>
> Best,
> Liuqing Yue
>
> On 2023/12/29 00:21:36 Xuanwo wrote:
> > Hello all,
> >
> > We've got positive feedback on the DISCUSS thread[1], I'd like to start
> an
> > official VOTE thread now.
> >
> > Below are some facts and project highlights from the incubation phase
> > as well as the draft resolution:
> >
> > - Currently, our community consists of 19 committers, including mentors,
> >   with 12 serving as PPMC members.
> > - At present, we boast 164 contributors.
> > - Throughout the incubation period, we've made 9 releases—averaging at
> >   least one per month.
> > - We've had 7 different release managers to date.
> > - Our software is in production use by 10 known entities and is a
> dependency
> >   for 263 GitHub projects and 18 crates.io packages.
> > - To date, we have opened 1,200+ issues with 1,100+ successfully
> resolved.
> > - We have submitted a total of 2,400+ PRs, most of them have been merged
> >   or closed.
> > - We have met all maturity criteria as outlined in [2].
> >
> > Please vote on the resolution pasted below to graduate Apache OpenDAL
> from
> > the incubator to the Top Level Project.
> >
> > [ ] +1 Graduate Apache OpenDAL from the Incubator.
> > [ ] +0 No opinion.
> > [ ] -1 Don't graduate Apache OpenDAL from the Incubator because ...
> >
> > This vote will open for at least 72 hours.
> >
> > Many thanks to our mentors and everyone else for their support.
> >
> > [1] https://lists.apache.org/thread/3lwt4zkm1ovoskrz77y69pwntvn27xvs
> > [2] https://opendal.apache.org/community/maturity
> >
> > ---
> >
> > Establish the Apache OpenDAL Project
> >
> > WHEREAS, the Board of Directors deems it to be in the best interests of
> > the Foundation and consistent with the Foundation's purpose to establish
> > a Project Management Committee charged with the creation and maintenance
> > of open-source software, for distribution at no charge to the public,
> > related to Open Data Access Layer: Access data freely, painlessly, and
> > efficiently.
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > (PMC), to be known as the "Apache OpenDAL Project", be and hereby is
> > established pursuant to Bylaws of the Foundation; and be it further
> >
> > RESOLVED, that the Apache OpenDAL Project be and hereby is responsible
> > for the creation and maintenance of software related to Open Data Access
> > Layer: Access data freely, painlessly, and efficiently; and be it
> > further
> >
> > RESOLVED, that the office of "Vice President, Apache OpenDAL" be and
> > hereby is created, the person holding such office to serve at the
> > direction of the Board of Directors as the chair of the Apache OpenDAL
> > Project, and to have primary responsibility for management of the
> > projects within the scope of responsibility of the Apache OpenDAL
> > Project; and be it further
> >
> > RESOLVED, that the persons listed immediately below be and hereby are
> > appointed to serve as the initial members of the Apache OpenDAL Project:
> >
> >  * Cai Lue   
> >  * Chojan Shang  
> >  * Han Xu
> >  * Hao Ding  
> >  * Jun Ouyang
> >  * Mingzhuo Yin  
> >  * Sheng Wu  
> >  * Sundy Li  
> >  * Ted Liu   
> >  * Willem Ning Jiang 
> >  * Xiangdong 
> >  * Xiaoqiao He   
> >  * Zheao Li  
> >  * Zili Chen 
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Hao Ding be appointed to
> > the office of Vice President, Apache OpenDAL, to serve in accordance
> > with and subject to the direction of the Board of Directors and the
> > Bylaws of the Foundation until death, resignation, retirement, removal
> > or disqualification, or until a successor is appointed; and be it
> > further
> >
> > RESOLVED, that the Apache OpenDAL Project be and hereby is tasked with
> > the migration and rationalization of the Apache Incubator OpenDAL
> > podling; and be it further
> >
> > RESOLVED, that all responsibilities pertaining to the Apache Incubator
> > OpenDAL podling encumbered upon the Apache Incubator PMC are hereafter
> > discharged.
> >
> > Xuanwo
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>