arrow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [arrow] branch master updated: ARROW-1371: [Website] Add "Powered By" page to the website
Date Tue, 14 Nov 2017 03:56:16 GMT
This is an automated email from the ASF dual-hosted git repository.

wesm pushed a commit to branch master
in repository

The following commit(s) were added to refs/heads/master by this push:
     new b18bbeb  ARROW-1371: [Website] Add "Powered By" page to the website
b18bbeb is described below

commit b18bbeba0ed8b76f6575bd0501de3beb1e6e60f5
Author: Korn, Uwe <>
AuthorDate: Mon Nov 13 22:56:13 2017 -0500

    ARROW-1371: [Website] Add "Powered By" page to the website
    Author: Korn, Uwe <>
    Author: Wes McKinney <>
    Author: Uwe L. Korn <>
    Closes #1280 from xhochy/ARROW-1371 and squashes the following commits:
    84a76e94 [Uwe L. Korn] Add Red Data Tools
    57338daa [Wes McKinney] Formatting
    522a3592 [Wes McKinney] Add a few more projects
    ad511ed2 [Korn, Uwe] Add GeoMesa and Dremio
    0e4f755c [Korn, Uwe] Add Ray and Spark
    ecabb167 [Korn, Uwe] ARROW-1371: [Website] Add "Powered By" page to the website
 site/_config.yml           |   1 +
 site/_includes/header.html |   1 +
 site/         | 126 +++++++++++++++++++++++++++++++++++++++++++++
 3 files changed, 128 insertions(+)

diff --git a/site/_config.yml b/site/_config.yml
index a6c5575..cbcf97d 100644
--- a/site/_config.yml
+++ b/site/_config.yml
@@ -30,6 +30,7 @@ exclude:
   - Gemfile
   - Gemfile.lock
   - _docs/format/*
+  - ruby
   - asf-site
   - scripts
diff --git a/site/_includes/header.html b/site/_includes/header.html
index 6c0ec30..03b3c87 100644
--- a/site/_includes/header.html
+++ b/site/_includes/header.html
@@ -27,6 +27,7 @@
             <li><a href="">Mailing
             <li><a href="">Slack Channel</a></li>
             <li><a href="{{ site.baseurl }}/committers/">Committers</a></li>
+            <li><a href="{{ site.baseurl }}/powered_by/">Powered By</a></li>
         <li class="dropdown">
diff --git a/site/ b/site/
new file mode 100644
index 0000000..38320c0
--- /dev/null
+++ b/site/
@@ -0,0 +1,126 @@
+layout: default
+{% comment %}
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements.  See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to you under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License.  You may obtain a copy of the License at
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+See the License for the specific language governing permissions and
+limitations under the License.
+{% endcomment %}
+## Powered By
+### Project and Product names using "Apache Arrow"
+Organizations creating products and projects for use with Apache Arrow, along
+with associated marketing materials, should take care to respect the trademark
+in "Apache Arrow" and its logo. Please refer to [ASF Trademarks Guidance][1]
+and associated [FAQ][2] for comprehensive and authoritative guidance on proper
+usage of ASF trademarks.
+Names that do not include "Apache Arrow" at all have no potential trademark
+issue with the Apache Arrow project. This is recommended.
+Names like "Apache Arrow BigCoProduct" are not OK, as are names including
+"Apache Arrow" in general. The above links, however, describe some exceptions,
+like for names such as "BigCoProduct, powered by Apache Arrow" or
+"BigCoProduct for Apache Arrow".
+It is common practice to create software identifiers (Maven coordinates, module
+names, etc.) like "arrow-foo". These are permitted. Nominative use of trademarks
+in descriptions is also always allowed, as in "BigCoProduct is a widget for
+Apache Arrow".
+### Open Source Projects
+To add yourself to the list, please email with your
+organization name, URL, a list of which Arrow components you are using, and a
+short description of your use case.
+* **[Apache Parquet][3]:** A columnar storage format available to any project
+  in the Hadoop ecosystem, regardless of the choice of data processing
+  framework, data model or programming language. The C++ and Java
+  implementation provide vectorized reads and write to/from Arrow data
+  structures.
+* **[Apache Spark][7]:** Apache Sparkā„¢ is a fast and general engine for
+  large-scale data processing. Spark uses Apache Arrow to
+  1. improve performance of conversion between Spark DataFrame and pandas DataFrame
+  2. enable a set of vectorized user-defined functions (`pandas_udf`) in PySpark.
+* **[Dask][15]:** Python library for parallel and distributed execution of
+  dynamic task graphs. Dask supports using pyarrow for accessing Parquet
+  files
+* **[GeoMesa][8]:** A suite of tools that enables large-scale geospatial query
+  and analytics on distributed computing systems. GeoMesa supports query
+  results in the Arrow IPC format, which can then be used for in-browser
+  visualizations and/or further analytics.
+* **[libgdf][14]:** A C library of CUDA-based analytics functions and GPU IPC
+  support for structured data. Uses the Arrow IPC format and targets the Arrow
+  memory layout in its analytic functions. This work is part of the [GPU Open
+  Analytics Initiative][11]
+* **[MapD][10]:** in-memory columnar SQL engine designed to run on GPUs. MapD
+  supports Arrow for data ingest and data interchange via CUDA IPC
+  handles. This work is part of the [GPU Open Analytics Initiative][11]
+* **[pandas][12]:** data analysis toolkit for Python programmers. pandas
+  supports reading and writing Parquet files using pyarrow. Several pandas
+  core developers are also contributors to Apache Arrow.
+* **[Ray][5]:** A flexible, high-performance distributed execution framework
+  with a focus on machine learning and AI applications. Uses Arrow to
+  efficiently store Python data structures containing large arrays of numerical
+  data. Data can be accessed with zero-copy by multiple processes using the
+  [Plasma shared memory object store][6] which originated from Ray and is part
+  of Arrow now.
+* **[Red Data Tools][16]:** A project that provides data processing
+  tools for Ruby. It provides [Red Arrow][17] that is a Ruby bindings
+  of Apache Arrow based on Apache Arrow GLib. Red Arrow is a core
+  library for it. It also provides many Ruby libraries to integrate
+  existing Ruby libraries with Apache Arrow. They use Red Arrow.
+* **[Turbodbc][4]:** Python module to access relational databases via the Open
+  Database Connectivity (ODBC) interface. It provides the ability to return
+  Arrow Tables and RecordBatches in addition to the Python Database API
+  Specification 2.0.
+### Companies and Organizations
+To add yourself to the list, please email with your
+organization name, URL, a list of which Arrow components you are using, and a
+short description of your use case.
+* **[Dremio][9]:** A self-service data platform. Dremio makes it easy for
+  users to discover, curate, accelerate, and share data from any source.
+  It includes a distributed SQL execution engine based on Apache Arrow.
+  Dremio reads data from any source (RDBMS, HDFS, S3, NoSQL) into Arrow
+  buffers, and provides fast SQL access via ODBC, JDBC, and REST for BI,
+  Python, R, and more (all backed by Apache Arrow).
+* **[Quilt Data][13]:** Quilt is a data package manager, designed to make
+  managing data as easy as managing code. It supports Parquet format via
+  pyarrow for data access.

To stop receiving notification emails like this one, please contact
['"" <>'].

View raw message