Re: [PR] Bump aws.version from 1.12.694 to 1.12.695 [tika]
THausherr merged PR #1710: URL: https://github.com/apache/tika/pull/1710 -- 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: dev-unsubscr...@tika.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Bump com.github.luben:zstd-jni from 1.5.6-1 to 1.5.6-2 [tika]
dependabot[bot] opened a new pull request, #1711: URL: https://github.com/apache/tika/pull/1711 Bumps [com.github.luben:zstd-jni](https://github.com/luben/zstd-jni) from 1.5.6-1 to 1.5.6-2. Commits https://github.com/luben/zstd-jni/commit/1ff893399707523b04ccd373ff6c3e659ec8;>1ff8933 Use cross-compile for i386 https://github.com/luben/zstd-jni/commit/b833326e2a4845fbeec6ca6f58e00049e4ee9c16;>b833326 Adding a getByReferenceBuffer() method. https://github.com/luben/zstd-jni/commit/2a262bf94c818919a6348bd232b63a238c7461fd;>2a262bf Add new constructor to ZstdDictCompress and ZstdDictDecompress that https://github.com/luben/zstd-jni/commit/a516a43567454f10eed8fe3c69d13e6b95a37060;>a516a43 Add back some inspection on MacOS, bump version https://github.com/luben/zstd-jni/commit/2e00ab12f38a28d23cbb1749200fb42880f929af;>2e00ab1 Enable tests on M1 MacOS https://github.com/luben/zstd-jni/commit/c76455c47f48e20fe7fc6e815a1c31300a46d546;>c76455c Add debugging in MacOS CI https://github.com/luben/zstd-jni/commit/ec1ddeb069f59727ecfcbeeb34ca3e6d8a481d49;>ec1ddeb Use the M1 MacOS runner to compile the aarch64 binary https://github.com/luben/zstd-jni/commit/fb6a35d89939c615dde306a8cbfc0a4de1b0c3c9;>fb6a35d Update also checkout and setup-qemu actions https://github.com/luben/zstd-jni/commit/7525a53f8bd144eabde2769ce0e87193be67cd35;>7525a53 setup-java v4 See full diff in https://github.com/luben/zstd-jni/compare/v1.5.6-1...v1.5.6-2;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- 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: dev-unsubscr...@tika.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Bump aws.version from 1.12.694 to 1.12.695 [tika]
dependabot[bot] opened a new pull request, #1710: URL: https://github.com/apache/tika/pull/1710 Bumps `aws.version` from 1.12.694 to 1.12.695. Updates `com.amazonaws:aws-java-sdk-s3` from 1.12.694 to 1.12.695 Changelog Sourced from https://github.com/aws/aws-sdk-java/blob/master/CHANGELOG.md;>com.amazonaws:aws-java-sdk-s3's changelog. 1.12.695 2024-04-04 AWS B2B Data Interchange Features Adding support for X12 5010 HIPAA EDI version and associated transaction sets. AWS Clean Rooms Service Features Feature: New schemaStatusDetails field to the existing Schema object that displays a status on Schema API responses to show whether a schema is queryable or not. New BatchGetSchemaAnalysisRule API to retrieve multiple schemaAnalysisRules using a single API call. Amazon EMR Containers Features This release adds support for integration with EKS AccessEntry APIs to enable automatic Cluster Access for EMR on EKS. Amazon Elastic Compute Cloud Features Amazon EC2 G6 instances powered by NVIDIA L4 Tensor Core GPUs can be used for a wide range of graphics-intensive and machine learning use cases. Gr6 instances also feature NVIDIA L4 GPUs and can be used for graphics workloads with higher memory requirements. Amazon Interactive Video Service Features API update to include an SRT ingest endpoint and passphrase for all channels. Amazon Verified Permissions Features Adds GroupConfiguration field to Identity Source API's Commits https://github.com/aws/aws-sdk-java/commit/f3f5543cc45a24aa122866677256486ecb6a1b41;>f3f5543 AWS SDK for Java 1.12.695 https://github.com/aws/aws-sdk-java/commit/b4ec2abf4911be236d3eb08e3f915dba738f265d;>b4ec2ab Update GitHub version number to 1.12.695-SNAPSHOT See full diff in https://github.com/aws/aws-sdk-java/compare/1.12.694...1.12.695;>compare view Updates `com.amazonaws:aws-java-sdk-transcribe` from 1.12.694 to 1.12.695 Changelog Sourced from https://github.com/aws/aws-sdk-java/blob/master/CHANGELOG.md;>com.amazonaws:aws-java-sdk-transcribe's changelog. 1.12.695 2024-04-04 AWS B2B Data Interchange Features Adding support for X12 5010 HIPAA EDI version and associated transaction sets. AWS Clean Rooms Service Features Feature: New schemaStatusDetails field to the existing Schema object that displays a status on Schema API responses to show whether a schema is queryable or not. New BatchGetSchemaAnalysisRule API to retrieve multiple schemaAnalysisRules using a single API call. Amazon EMR Containers Features This release adds support for integration with EKS AccessEntry APIs to enable automatic Cluster Access for EMR on EKS. Amazon Elastic Compute Cloud Features Amazon EC2 G6 instances powered by NVIDIA L4 Tensor Core GPUs can be used for a wide range of graphics-intensive and machine learning use cases. Gr6 instances also feature NVIDIA L4 GPUs and can be used for graphics workloads with higher memory requirements. Amazon Interactive Video Service Features API update to include an SRT ingest endpoint and passphrase for all channels. Amazon Verified Permissions Features Adds GroupConfiguration field to Identity Source API's Commits https://github.com/aws/aws-sdk-java/commit/f3f5543cc45a24aa122866677256486ecb6a1b41;>f3f5543 AWS SDK for Java 1.12.695 https://github.com/aws/aws-sdk-java/commit/b4ec2abf4911be236d3eb08e3f915dba738f265d;>b4ec2ab Update GitHub version number to 1.12.695-SNAPSHOT See full diff in https://github.com/aws/aws-sdk-java/compare/1.12.694...1.12.695;>compare view Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
Re: [PR] Support for adding custom tika configuration [tika-helm]
lewismc commented on code in PR #15:
URL: https://github.com/apache/tika-helm/pull/15#discussion_r1552678442
##
templates/configmap.yaml:
##
@@ -0,0 +1,9 @@
+{{- if .Values.tikaConfig }}
Review Comment:
@ahilmathew please add Apache License v2 file header. Thank you
--
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: dev-unsubscr...@tika.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Re: [PR] Support for adding custom tika configuration [tika-helm]
ahilmathew commented on PR #15: URL: https://github.com/apache/tika-helm/pull/15#issuecomment-2038203402 @lewismc Thanks for the comments. I've updated `values.yaml` to include the configuration from https://tika.apache.org/2.9.1/configuring.html. Let me know if there is a specific configuration you would like to be included as default. -- 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: dev-unsubscr...@tika.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (TIKA-4235) Add pipeline parameter to OpenSearch emitter
[ https://issues.apache.org/jira/browse/TIKA-4235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834041#comment-17834041 ] ASF GitHub Bot commented on TIKA-4235: -- tballison opened a new pull request, #1709: URL: https://github.com/apache/tika/pull/1709 Thanks for your contribution to [Apache Tika](https://tika.apache.org/)! Your help is appreciated! Before opening the pull request, please verify that * there is an open issue on the [Tika issue tracker](https://issues.apache.org/jira/projects/TIKA) which describes the problem or the improvement. We cannot accept pull requests without an issue because the change wouldn't be listed in the release notes. * the issue ID (`TIKA-`) - is referenced in the title of the pull request - and placed in front of your commit messages surrounded by square brackets (`[TIKA-] Issue or pull request title`) * commits are squashed into a single one (or few commits for larger changes) * Tika is successfully built and unit tests pass by running `mvn clean test` * there should be no conflicts when merging the pull request branch into the *recent* `main` branch. If there are conflicts, please try to rebase the pull request branch on top of a freshly pulled `main` branch * if you add new module that downstream users will depend upon add it to relevant group in `tika-bom/pom.xml`. We will be able to faster integrate your pull request if these conditions are met. If you have any questions how to fix your problem or about using Tika in general, please sign up for the [Tika mailing list](http://tika.apache.org/mail-lists.html). Thanks! > Add pipeline parameter to OpenSearch emitter > > > Key: TIKA-4235 > URL: https://issues.apache.org/jira/browse/TIKA-4235 > Project: Tika > Issue Type: New Feature >Reporter: Tim Allison >Priority: Trivial > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] TIKA-4235 [tika]
tballison opened a new pull request, #1709: URL: https://github.com/apache/tika/pull/1709 Thanks for your contribution to [Apache Tika](https://tika.apache.org/)! Your help is appreciated! Before opening the pull request, please verify that * there is an open issue on the [Tika issue tracker](https://issues.apache.org/jira/projects/TIKA) which describes the problem or the improvement. We cannot accept pull requests without an issue because the change wouldn't be listed in the release notes. * the issue ID (`TIKA-`) - is referenced in the title of the pull request - and placed in front of your commit messages surrounded by square brackets (`[TIKA-] Issue or pull request title`) * commits are squashed into a single one (or few commits for larger changes) * Tika is successfully built and unit tests pass by running `mvn clean test` * there should be no conflicts when merging the pull request branch into the *recent* `main` branch. If there are conflicts, please try to rebase the pull request branch on top of a freshly pulled `main` branch * if you add new module that downstream users will depend upon add it to relevant group in `tika-bom/pom.xml`. We will be able to faster integrate your pull request if these conditions are met. If you have any questions how to fix your problem or about using Tika in general, please sign up for the [Tika mailing list](http://tika.apache.org/mail-lists.html). Thanks! -- 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: dev-unsubscr...@tika.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (TIKA-4235) Add pipeline parameter to OpenSearch emitter
Tim Allison created TIKA-4235: - Summary: Add pipeline parameter to OpenSearch emitter Key: TIKA-4235 URL: https://issues.apache.org/jira/browse/TIKA-4235 Project: Tika Issue Type: New Feature Reporter: Tim Allison -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (TIKA-4232) Create and execute unit tests for tika-helm
[ https://issues.apache.org/jira/browse/TIKA-4232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17833960#comment-17833960 ] ASF GitHub Bot commented on TIKA-4232: -- lewismc commented on PR #17: URL: https://github.com/apache/tika-helm/pull/17#issuecomment-2037434458 Blocked by https://issues.apache.org/jira/browse/INFRA-25667 > Create and execute unit tests for tika-helm > --- > > Key: TIKA-4232 > URL: https://issues.apache.org/jira/browse/TIKA-4232 > Project: Tika > Issue Type: Improvement > Components: tika-helm >Reporter: Lewis John McGibbney >Assignee: Lewis John McGibbney >Priority: Major > Fix For: 2.9.2 > > > The goal is to execute chart unit tests against each tika-helm pull request. > I found the [Helm Unit > Tests|[https://github.com/marketplace/actions/helm-unit-tests]] GitHub Action > which uses [https://github.com/helm-unittest/helm-unittest] as a Helm plugin. > The PR will consist of one or more unit tests automated via the GitHub action. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] 2.9.2.0 release [tika-helm]
lewismc commented on PR #19: URL: https://github.com/apache/tika-helm/pull/19#issuecomment-2037436559 Will revisit this ticket once we have closed out https://github.com/apache/tika-helm/pull/19 -- 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: dev-unsubscr...@tika.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] TIKA-4232 Create and execute unit tests for tika-helm [tika-helm]
lewismc commented on PR #17: URL: https://github.com/apache/tika-helm/pull/17#issuecomment-2037434458 Blocked by https://issues.apache.org/jira/browse/INFRA-25667 -- 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: dev-unsubscr...@tika.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (TIKA-4233) Check tika-helm for deprecated k8s APIs
[ https://issues.apache.org/jira/browse/TIKA-4233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17833959#comment-17833959 ] ASF GitHub Bot commented on TIKA-4233: -- lewismc commented on PR #18: URL: https://github.com/apache/tika-helm/pull/18#issuecomment-2037433774 Blocked by https://issues.apache.org/jira/browse/INFRA-25667 > Check tika-helm for deprecated k8s APIs > --- > > Key: TIKA-4233 > URL: https://issues.apache.org/jira/browse/TIKA-4233 > Project: Tika > Issue Type: New Feature > Components: tika-helm >Reporter: Lewis John McGibbney >Assignee: Lewis John McGibbney >Priority: Major > Fix For: 2.9.2 > > > It is useful to know when a Helm Chart uses deprecated k8s APIs. A check for > this would be ideal. The “Check deprecated k8s APIs” GitHub action > accomplishes this. > [https://github.com/marketplace/actions/check-deprecated-k8s-apis] -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] TIKA-4233 Check tika-helm for deprecated k8s APIs [tika-helm]
lewismc commented on PR #18: URL: https://github.com/apache/tika-helm/pull/18#issuecomment-2037433774 Blocked by https://issues.apache.org/jira/browse/INFRA-25667 -- 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: dev-unsubscr...@tika.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Support for adding custom tika configuration [tika-helm]
lewismc commented on PR #15: URL: https://github.com/apache/tika-helm/pull/15#issuecomment-2037419324 @ahilmathew please sync with `main` branch and also include the default oncfiguration in `values.yaml`. Thank you -- 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: dev-unsubscr...@tika.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Support for adding custom tika configuration [tika-helm]
lewismc commented on PR #15: URL: https://github.com/apache/tika-helm/pull/15#issuecomment-2037419625 @t-l-k understood -- 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: dev-unsubscr...@tika.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Resolved] (TIKA-4234) Further improvements to jdbc pipes reporter
[ https://issues.apache.org/jira/browse/TIKA-4234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Allison resolved TIKA-4234. --- Fix Version/s: 3.0.0 Resolution: Fixed > Further improvements to jdbc pipes reporter > --- > > Key: TIKA-4234 > URL: https://issues.apache.org/jira/browse/TIKA-4234 > Project: Tika > Issue Type: Improvement >Reporter: Tim Allison >Priority: Trivial > Fix For: 3.0.0 > > > Allow users to set the table name. > Allow users to choose whether or not to drop+create the table via the > reporter or whether they're responsible for creating the table. > Allow users to configure insert/upsert/update. The default is "insert id, > status, timestamp". > This and the earlier jdbc reporter introduce breaking changes and will only > be applied to 3.x. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] TIKA-4234 [tika]
tballison merged PR #1708: URL: https://github.com/apache/tika/pull/1708 -- 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: dev-unsubscr...@tika.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (TIKA-4234) Further improvements to jdbc pipes reporter
[ https://issues.apache.org/jira/browse/TIKA-4234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17833940#comment-17833940 ] ASF GitHub Bot commented on TIKA-4234: -- tballison opened a new pull request, #1708: URL: https://github.com/apache/tika/pull/1708 Thanks for your contribution to [Apache Tika](https://tika.apache.org/)! Your help is appreciated! Before opening the pull request, please verify that * there is an open issue on the [Tika issue tracker](https://issues.apache.org/jira/projects/TIKA) which describes the problem or the improvement. We cannot accept pull requests without an issue because the change wouldn't be listed in the release notes. * the issue ID (`TIKA-`) - is referenced in the title of the pull request - and placed in front of your commit messages surrounded by square brackets (`[TIKA-] Issue or pull request title`) * commits are squashed into a single one (or few commits for larger changes) * Tika is successfully built and unit tests pass by running `mvn clean test` * there should be no conflicts when merging the pull request branch into the *recent* `main` branch. If there are conflicts, please try to rebase the pull request branch on top of a freshly pulled `main` branch * if you add new module that downstream users will depend upon add it to relevant group in `tika-bom/pom.xml`. We will be able to faster integrate your pull request if these conditions are met. If you have any questions how to fix your problem or about using Tika in general, please sign up for the [Tika mailing list](http://tika.apache.org/mail-lists.html). Thanks! > Further improvements to jdbc pipes reporter > --- > > Key: TIKA-4234 > URL: https://issues.apache.org/jira/browse/TIKA-4234 > Project: Tika > Issue Type: Improvement >Reporter: Tim Allison >Priority: Trivial > > Allow users to set the table name. > Allow users to choose whether or not to drop+create the table via the > reporter or whether they're responsible for creating the table. > Allow users to configure insert/upsert/update. The default is "insert id, > status, timestamp". > This and the earlier jdbc reporter introduce breaking changes and will only > be applied to 3.x. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] TIKA-4234 [tika]
tballison opened a new pull request, #1708: URL: https://github.com/apache/tika/pull/1708 Thanks for your contribution to [Apache Tika](https://tika.apache.org/)! Your help is appreciated! Before opening the pull request, please verify that * there is an open issue on the [Tika issue tracker](https://issues.apache.org/jira/projects/TIKA) which describes the problem or the improvement. We cannot accept pull requests without an issue because the change wouldn't be listed in the release notes. * the issue ID (`TIKA-`) - is referenced in the title of the pull request - and placed in front of your commit messages surrounded by square brackets (`[TIKA-] Issue or pull request title`) * commits are squashed into a single one (or few commits for larger changes) * Tika is successfully built and unit tests pass by running `mvn clean test` * there should be no conflicts when merging the pull request branch into the *recent* `main` branch. If there are conflicts, please try to rebase the pull request branch on top of a freshly pulled `main` branch * if you add new module that downstream users will depend upon add it to relevant group in `tika-bom/pom.xml`. We will be able to faster integrate your pull request if these conditions are met. If you have any questions how to fix your problem or about using Tika in general, please sign up for the [Tika mailing list](http://tika.apache.org/mail-lists.html). Thanks! -- 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: dev-unsubscr...@tika.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (TIKA-4234) Further improvements to jdbc pipes reporter
Tim Allison created TIKA-4234: - Summary: Further improvements to jdbc pipes reporter Key: TIKA-4234 URL: https://issues.apache.org/jira/browse/TIKA-4234 Project: Tika Issue Type: Improvement Reporter: Tim Allison Allow users to set the table name. Allow users to choose whether or not to drop+create the table via the reporter or whether they're responsible for creating the table. Allow users to configure insert/upsert/update. The default is "insert id, status, timestamp". This and the earlier jdbc reporter introduce breaking changes and will only be applied to 3.x. -- This message was sent by Atlassian Jira (v8.20.10#820010)
