You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@iceberg.apache.org by "qinghui-xu (via GitHub)" <gi...@apache.org> on 2025/10/10 13:58:43 UTC

[PR] README: recommendation for packaging spark jobs [iceberg]

qinghui-xu opened a new pull request, #14292:
URL: https://github.com/apache/iceberg/pull/14292

   Sometimes iceberg may use verisons of parquet, avro, or other libs that are incompatible with what's deployed in Spark runtime. Users should package only iceberg-spark-runtime (it shaded transitive deps) into the uberjar to avoid such issue.
   cf. https://github.com/apache/iceberg/issues/14232


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org


Re: [PR] Docs: recommendation for packaging uberjars [iceberg]

Posted by "nastra (via GitHub)" <gi...@apache.org>.
nastra commented on code in PR #14292:
URL: https://github.com/apache/iceberg/pull/14292#discussion_r2454632855


##########
README.md:
##########
@@ -71,8 +71,8 @@ Iceberg table support is organized in library modules:
 
 Iceberg also has modules for adding Iceberg support to processing engines:
 
-* `iceberg-spark` is an implementation of Spark's Datasource V2 API for Iceberg with submodules for each spark versions (use runtime jars for a shaded version)
-* `iceberg-flink` contains classes for integrating with Apache Flink (use iceberg-flink-runtime for a shaded version)
+* `iceberg-spark` is an implementation of Spark's Datasource V2 API for Iceberg with submodules for each spark versions (use runtime jars for a shaded version to avoid dependency conflicts, see [the documentation](https://iceberg.apache.org/multi-engine-support/#runtime-jar))

Review Comment:
   ```suggestion
   * `iceberg-spark` is an implementation of Spark's Datasource V2 API for Iceberg with submodules for each spark versions (use [runtime jars](https://iceberg.apache.org/multi-engine-support/#runtime-jar) for a shaded version to avoid dependency conflicts)
   ```



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org


Re: [PR] README: recommendation for packaging spark jobs [iceberg]

Posted by "qinghui-xu (via GitHub)" <gi...@apache.org>.
qinghui-xu commented on code in PR #14292:
URL: https://github.com/apache/iceberg/pull/14292#discussion_r2448882237


##########
README.md:
##########
@@ -72,6 +72,7 @@ Iceberg table support is organized in library modules:
 Iceberg also has modules for adding Iceberg support to processing engines:
 
 * `iceberg-spark` is an implementation of Spark's Datasource V2 API for Iceberg with submodules for each spark versions (use runtime jars for a shaded version)
+    * When packaging user projects, keep only `iceberg-spark-runtime` in the uberjar. All other functional modules such as `iceberg-core` or `iceberg-parquet` (and their transitive dependencies) should be excluded from uberjar, because some libraries (`parquet`, `avro`, etc) they use may be of versions incompatible with those provided in Spark runtime classpath.

Review Comment:
   Thanks for the reply. I'd like to use less strong wording for the last phrase "they may lead to dependency mismatches/conflicts on runtime classpath" because with previous versions of iceberg (up to 1.8) I did not encounter such issues with my crooked setup.
   
   



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org


Re: [PR] README: recommendation for packaging spark jobs [iceberg]

Posted by "qinghui-xu (via GitHub)" <gi...@apache.org>.
qinghui-xu commented on code in PR #14292:
URL: https://github.com/apache/iceberg/pull/14292#discussion_r2449211148


##########
README.md:
##########
@@ -72,7 +72,9 @@ Iceberg table support is organized in library modules:
 Iceberg also has modules for adding Iceberg support to processing engines:
 
 * `iceberg-spark` is an implementation of Spark's Datasource V2 API for Iceberg with submodules for each spark versions (use runtime jars for a shaded version)
+    * When packaging user projects in an uberjar, only the `iceberg-spark-runtime` jar and potentially one of the storage-specific bundles, such as `iceberg-aws-bundle` or `iceberg-gcp-bundle` are needed, as suggested by [the documentation](https://iceberg.apache.org/multi-engine-support/#runtime-jar). No other Iceberg modules, such as `iceberg-core` or `iceberg-parquet` (and their transitive dependencies) are needed, as they may lead to dependency version mismatches/conflicts on the runtime classpath.

Review Comment:
   I agree it seems a bit redundant as information. But I'd like to highlight that we should exclude other modules from runtime classpath (eg. uberjar). Maybe I should put this into the [doc](https://iceberg.apache.org/multi-engine-support/#runtime-jar) instead?



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org


Re: [PR] Docs: recommendation for packaging uberjars [iceberg]

Posted by "qinghui-xu (via GitHub)" <gi...@apache.org>.
qinghui-xu commented on code in PR #14292:
URL: https://github.com/apache/iceberg/pull/14292#discussion_r2455213225


##########
site/docs/multi-engine-support.md:
##########
@@ -42,6 +42,10 @@ Iceberg provides a runtime connector jar for each supported version of Spark, Fl
 When using Iceberg with these engines, the runtime jar is the only addition to the classpath needed in addition to vendor dependencies.
 For example, to use Iceberg with Spark 3.5 and AWS integrations, `iceberg-spark-runtime-3.5_2.12` and AWS SDK dependencies are needed for the Spark installation.
 
+> ℹ️ It's important to make sure that only the runtime jars (plus storage specific bundles if needed, eg. `iceberg-aws-bundle` or `iceberg-gcp-bundle`) are included in the runtime classpath.

Review Comment:
   <img width="1710" height="900" alt="screenshot-iceberg-doc" src="https://github.com/user-attachments/assets/0e3c8359-dfc2-4f23-a3a4-22dfead27e4b" />
   It should look like this.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org


Re: [PR] Docs: recommendation for packaging uberjars [iceberg]

Posted by "nastra (via GitHub)" <gi...@apache.org>.
nastra merged PR #14292:
URL: https://github.com/apache/iceberg/pull/14292


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org


Re: [PR] README: recommendation for packaging spark jobs [iceberg]

Posted by "nastra (via GitHub)" <gi...@apache.org>.
nastra commented on code in PR #14292:
URL: https://github.com/apache/iceberg/pull/14292#discussion_r2446909081


##########
README.md:
##########
@@ -72,6 +72,7 @@ Iceberg table support is organized in library modules:
 Iceberg also has modules for adding Iceberg support to processing engines:
 
 * `iceberg-spark` is an implementation of Spark's Datasource V2 API for Iceberg with submodules for each spark versions (use runtime jars for a shaded version)
+    * When packaging user projects, keep only `iceberg-spark-runtime` in the uberjar. All other functional modules such as `iceberg-core` or `iceberg-parquet` (and their transitive dependencies) should be excluded from uberjar, because some libraries (`parquet`, `avro`, etc) they use may be of versions incompatible with those provided in Spark runtime classpath.

Review Comment:
   we should probably add the same wording for `iceberg-flink` below



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org


Re: [PR] Docs: recommendation for packaging uberjars [iceberg]

Posted by "nastra (via GitHub)" <gi...@apache.org>.
nastra commented on code in PR #14292:
URL: https://github.com/apache/iceberg/pull/14292#discussion_r2454628426


##########
site/docs/multi-engine-support.md:
##########
@@ -42,6 +42,10 @@ Iceberg provides a runtime connector jar for each supported version of Spark, Fl
 When using Iceberg with these engines, the runtime jar is the only addition to the classpath needed in addition to vendor dependencies.
 For example, to use Iceberg with Spark 3.5 and AWS integrations, `iceberg-spark-runtime-3.5_2.12` and AWS SDK dependencies are needed for the Spark installation.
 
+> ℹ️ It's important to make sure that only the runtime jars (plus storage specific bundles if needed, eg. `iceberg-aws-bundle` or `iceberg-gcp-bundle`) are included in the runtime classpath.

Review Comment:
   how does this page render? Can you provide a screenshot when running the site locally?



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org


Re: [PR] README: recommendation for packaging spark jobs [iceberg]

Posted by "nastra (via GitHub)" <gi...@apache.org>.
nastra commented on code in PR #14292:
URL: https://github.com/apache/iceberg/pull/14292#discussion_r2450486653


##########
README.md:
##########
@@ -72,7 +72,9 @@ Iceberg table support is organized in library modules:
 Iceberg also has modules for adding Iceberg support to processing engines:
 
 * `iceberg-spark` is an implementation of Spark's Datasource V2 API for Iceberg with submodules for each spark versions (use runtime jars for a shaded version)
+    * When packaging user projects in an uberjar, only the `iceberg-spark-runtime` jar and potentially one of the storage-specific bundles, such as `iceberg-aws-bundle` or `iceberg-gcp-bundle` are needed, as suggested by [the documentation](https://iceberg.apache.org/multi-engine-support/#runtime-jar). No other Iceberg modules, such as `iceberg-core` or `iceberg-parquet` (and their transitive dependencies) are needed, as they may lead to dependency version mismatches/conflicts on the runtime classpath.

Review Comment:
   Yes just add it to the linked doc and here please only add the link as otherwise we're duplicating information



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org


Re: [PR] Docs: recommendation for packaging uberjars [iceberg]

Posted by "qinghui-xu (via GitHub)" <gi...@apache.org>.
qinghui-xu commented on code in PR #14292:
URL: https://github.com/apache/iceberg/pull/14292#discussion_r2454423387


##########
README.md:
##########
@@ -72,7 +72,9 @@ Iceberg table support is organized in library modules:
 Iceberg also has modules for adding Iceberg support to processing engines:
 
 * `iceberg-spark` is an implementation of Spark's Datasource V2 API for Iceberg with submodules for each spark versions (use runtime jars for a shaded version)
+    * When packaging user projects in an uberjar, only the `iceberg-spark-runtime` jar and potentially one of the storage-specific bundles, such as `iceberg-aws-bundle` or `iceberg-gcp-bundle` are needed, as suggested by [the documentation](https://iceberg.apache.org/multi-engine-support/#runtime-jar). No other Iceberg modules, such as `iceberg-core` or `iceberg-parquet` (and their transitive dependencies) are needed, as they may lead to dependency version mismatches/conflicts on the runtime classpath.

Review Comment:
   Updated the site/docs and add a pointer in the README.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org


Re: [PR] Docs: recommendation for packaging uberjars [iceberg]

Posted by "nastra (via GitHub)" <gi...@apache.org>.
nastra commented on code in PR #14292:
URL: https://github.com/apache/iceberg/pull/14292#discussion_r2454634297


##########
README.md:
##########
@@ -71,8 +71,8 @@ Iceberg table support is organized in library modules:
 
 Iceberg also has modules for adding Iceberg support to processing engines:
 
-* `iceberg-spark` is an implementation of Spark's Datasource V2 API for Iceberg with submodules for each spark versions (use runtime jars for a shaded version)
-* `iceberg-flink` contains classes for integrating with Apache Flink (use iceberg-flink-runtime for a shaded version)
+* `iceberg-spark` is an implementation of Spark's Datasource V2 API for Iceberg with submodules for each spark versions (use runtime jars for a shaded version to avoid dependency conflicts, see [the documentation](https://iceberg.apache.org/multi-engine-support/#runtime-jar))
+* `iceberg-flink` contains classes for integrating with Apache Flink (use iceberg-flink-runtime for a shaded version, see [the documentation](https://iceberg.apache.org/multi-engine-support/#runtime-jar))

Review Comment:
   ```suggestion
   * `iceberg-flink` contains classes for integrating with Apache Flink (use [iceberg-flink-runtime](https://iceberg.apache.org/multi-engine-support/#runtime-jar) for a shaded version)
   ```



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org


Re: [PR] Docs: recommendation for packaging uberjars [iceberg]

Posted by "nastra (via GitHub)" <gi...@apache.org>.
nastra commented on code in PR #14292:
URL: https://github.com/apache/iceberg/pull/14292#discussion_r2454630455


##########
site/docs/multi-engine-support.md:
##########
@@ -42,6 +42,10 @@ Iceberg provides a runtime connector jar for each supported version of Spark, Fl
 When using Iceberg with these engines, the runtime jar is the only addition to the classpath needed in addition to vendor dependencies.
 For example, to use Iceberg with Spark 3.5 and AWS integrations, `iceberg-spark-runtime-3.5_2.12` and AWS SDK dependencies are needed for the Spark installation.
 
+> ℹ️ It's important to make sure that only the runtime jars (plus storage specific bundles if needed, eg. `iceberg-aws-bundle` or `iceberg-gcp-bundle`) are included in the runtime classpath.
+> All other modules should be excluded as they may introduce dependency version conflicts with engine runtimes.
+> For example, when packaging uberjar for a Spark application, we should include `iceberg-spark-runtime` and exclude modules such as `iceberg-core` or `iceberg-parquet`.

Review Comment:
   ```suggestion
   > For example, when packaging an uberjar for a Spark application, only include `iceberg-spark-runtime` and exclude modules such as `iceberg-core` or `iceberg-parquet`.
   ```



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org


Re: [PR] README: recommendation for packaging spark jobs [iceberg]

Posted by "qinghui-xu (via GitHub)" <gi...@apache.org>.
qinghui-xu commented on PR #14292:
URL: https://github.com/apache/iceberg/pull/14292#issuecomment-3422495564

   Could somebody provide some feedback? Thanks a lot!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org


Re: [PR] README: recommendation for packaging spark jobs [iceberg]

Posted by "qinghui-xu (via GitHub)" <gi...@apache.org>.
qinghui-xu commented on PR #14292:
URL: https://github.com/apache/iceberg/pull/14292#issuecomment-3390315346

   cc @nastra @RussellSpitzer 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org


Re: [PR] README: recommendation for packaging spark jobs [iceberg]

Posted by "nastra (via GitHub)" <gi...@apache.org>.
nastra commented on code in PR #14292:
URL: https://github.com/apache/iceberg/pull/14292#discussion_r2446907723


##########
README.md:
##########
@@ -72,6 +72,7 @@ Iceberg table support is organized in library modules:
 Iceberg also has modules for adding Iceberg support to processing engines:
 
 * `iceberg-spark` is an implementation of Spark's Datasource V2 API for Iceberg with submodules for each spark versions (use runtime jars for a shaded version)
+    * When packaging user projects, keep only `iceberg-spark-runtime` in the uberjar. All other functional modules such as `iceberg-core` or `iceberg-parquet` (and their transitive dependencies) should be excluded from uberjar, because some libraries (`parquet`, `avro`, etc) they use may be of versions incompatible with those provided in Spark runtime classpath.

Review Comment:
   ```suggestion
       * When packaging user projects in an uberjar, only the `iceberg-spark-runtime` jar and potentially one of the storage-specific bundles, such as `iceberg-aws-bundle` or `iceberg-gcp-bundle` are needed. No other Iceberg modules, such as `iceberg-core` or `iceberg-parquet` (and their transitive dependencies) are needed, as this will lead to dependency mismatches/conflicts on the classpath.
   ```



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org


Re: [PR] README: recommendation for packaging spark jobs [iceberg]

Posted by "nastra (via GitHub)" <gi...@apache.org>.
nastra commented on PR #14292:
URL: https://github.com/apache/iceberg/pull/14292#issuecomment-3426910802

   thanks for pointing that out @manuzhang. @qinghui-xu can you just add a link to the respective section of the docs then?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org


Re: [PR] README: recommendation for packaging spark jobs [iceberg]

Posted by "nastra (via GitHub)" <gi...@apache.org>.
nastra commented on code in PR #14292:
URL: https://github.com/apache/iceberg/pull/14292#discussion_r2448925894


##########
README.md:
##########
@@ -72,7 +72,9 @@ Iceberg table support is organized in library modules:
 Iceberg also has modules for adding Iceberg support to processing engines:
 
 * `iceberg-spark` is an implementation of Spark's Datasource V2 API for Iceberg with submodules for each spark versions (use runtime jars for a shaded version)
+    * When packaging user projects in an uberjar, only the `iceberg-spark-runtime` jar and potentially one of the storage-specific bundles, such as `iceberg-aws-bundle` or `iceberg-gcp-bundle` are needed, as suggested by [the documentation](https://iceberg.apache.org/multi-engine-support/#runtime-jar). No other Iceberg modules, such as `iceberg-core` or `iceberg-parquet` (and their transitive dependencies) are needed, as they may lead to dependency version mismatches/conflicts on the runtime classpath.

Review Comment:
   I think we can remove this entire subsection and rather add a link to the line above which then links to the respective section: `... for each spark version (use [runtime jars](link goes here) for a shaded version)`
   
   And then we can do the same for `iceberg-flink-runtime` below



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org


Re: [PR] README: recommendation for packaging spark jobs [iceberg]

Posted by "manuzhang (via GitHub)" <gi...@apache.org>.
manuzhang commented on PR #14292:
URL: https://github.com/apache/iceberg/pull/14292#issuecomment-3426563687

   We actually have guidance at https://iceberg.apache.org/multi-engine-support/#runtime-jar. The README is not up-to-date. Shall we link to docs site in README?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org