-
Notifications
You must be signed in to change notification settings - Fork 588
HDDS-12004. [Doc] Other applications known to work with Ozone #8042
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,63 @@ | ||
| --- | ||
| title: Third-Party Integrations | ||
| weight: 4 | ||
| menu: | ||
| main: | ||
| parent: "Application Integrations" | ||
| --- | ||
| <!--- | ||
| 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 | ||
|
|
||
| http://www.apache.org/licenses/LICENSE-2.0 | ||
|
|
||
| Unless required by applicable law or agreed to in writing, software | ||
| distributed under the License is distributed on an "AS IS" BASIS, | ||
| WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | ||
| See the License for the specific language governing permissions and | ||
| limitations under the License. | ||
| --> | ||
|
|
||
| Here is a non-exhaustive list of third-party tools and applications that can be integrated with Ozone: | ||
|
|
||
| These integrations are not maintained by the Apache Ozone community. If you have any questions or issues, please contact the respective tool or application maintainers. | ||
|
|
||
| ## Open Source | ||
|
|
||
| * Apache NiFi | ||
|
|
||
| Apache NiFi adds support for Ozone in version 1.13.0. | ||
|
|
||
| Because Ozone file system is a Hadoop-compatible file system (HCFS), You can use the PutHDFS or the PutCDPObjectStore processor to move your data to Ozone. | ||
|
|
||
| For more information, see the [Pushing data to Ozone using Apache NiFi](https://docs.cloudera.com/cfm/4.0.0/nifi-ozone/topics/cfm-nifi-ozone-move-data.html) documentation. | ||
| * Apache Flink | ||
|
|
||
| Apache Flink can access Ozone as a Hadoop compatible file system. | ||
|
|
||
| Because Ozone does not yet support truncate() API, to use Ozone ofs as a DataStream connector, you must select OnCheckpointRollingPolicy. For example: | ||
|
|
||
| ```java | ||
| final StreamingFileSink<String> sink = StreamingFileSink | ||
| .forRowFormat(new Path("ofs:///ozone1/vol1/bucket1/flink"), new SimpleStringEncoder<String>("UTF-8")) | ||
| .withRollingPolicy(OnCheckpointRollingPolicy.build()) // Roll file on checkpoint | ||
| .build(); | ||
| ``` | ||
|
|
||
| For more information, see the [File Systems](https://nightlies.apache.org/flink/flink-docs-stable/docs/deployment/filesystems/overview/) documentation. | ||
|
|
||
| * PyArrow https://hackmd.io/@cxorm/cxorm | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is just someone's personal note, and uses o3fs which is not recommended. If we want to detail pyarrow support, it would be better to document it ourselves.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. moved & rewrote the PyArrow section here: #8556 |
||
| * Cloudera Hue can access Ozone through Ozone HTTPFS interface https://gethue.com/blog/discover-the-power-of-apache-ozone-using-the-hue-file-browser/ | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We can also convert this into a top level docs page and test it. This is more of a blog than a docs link. |
||
| * Alluxio https://docs.alluxio.io/os/user/stable/en/ufs/Ozone.html | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The banner at the top says these are old/archived docs. The current version has no mention of Ozone, likely because it fits under the HDFS and S3 sections already.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Interesting... as far as I can tell that doc I referred to is a "stable" version, and I can tell the Ozone support is still in the current codebase: https://github.com/Alluxio/alluxio/tree/main/underfs/ozone |
||
|
|
||
| ## Commercial | ||
| * Teradata https://docs.teradata.com/r/Enterprise_IntelliFlex_VMware/Teradata-VantageTM-Native-Object-Store-Getting-Started-Guide-17.20 | ||
| * Starburst https://docs.starburst.io/latest/connector/starburst-ozone.html | ||
|
Comment on lines
+58
to
+59
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. There's not much Ozone specific on these pages. They would probably be better suited as examples given under the S3 integration section. |
||
|
|
||
| ## Via Ozone S3 Gateway | ||
| Various applications can access Ozone via the S3 Gateway, which opens up Ozone to more cloud native use cases. | ||
| For example, send Fluentd logs to Ozone S3 Gateway. | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These open source options all seem like they should have dedicated pages under the Integrations section. I don't see why Hive or Impala would get their own page while Nifi or Flink would not.