[GitHub] [tika] THausherr merged pull request #804: Bump aws.version from 1.12.344 to 1.12.345
THausherr merged PR #804: URL: https://github.com/apache/tika/pull/804 -- 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
[GitHub] [tika] THausherr merged pull request #805: Bump sqlite-jdbc from 3.39.4.0 to 3.39.4.1
THausherr merged PR #805: URL: https://github.com/apache/tika/pull/805 -- 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
[GitHub] [tika] THausherr merged pull request #806: Bump google-cloud-storage from 2.15.0 to 2.15.1
THausherr merged PR #806: URL: https://github.com/apache/tika/pull/806 -- 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
[GitHub] [tika] dependabot[bot] opened a new pull request, #806: Bump google-cloud-storage from 2.15.0 to 2.15.1
dependabot[bot] opened a new pull request, #806: URL: https://github.com/apache/tika/pull/806 Bumps [google-cloud-storage](https://github.com/googleapis/java-storage) from 2.15.0 to 2.15.1. Release notes Sourced from https://github.com/googleapis/java-storage/releases;>google-cloud-storage's releases. v2.15.1 https://github.com/googleapis/java-storage/compare/v2.15.0...v2.15.1;>2.15.1 (2022-11-17) Bug Fixes Disable REGAPIC transport in storage v2 (https://github-redirect.dependabot.com/googleapis/java-storage/issues/1762;>#1762) (https://github.com/googleapis/java-storage/commit/13d630e7ce89273c292acca7a7e048218ece4182;>13d630e) Update GrpcStorageImpl#get(BlobId) to return null on 404 (https://github-redirect.dependabot.com/googleapis/java-storage/issues/1772;>#1772) (https://github.com/googleapis/java-storage/commit/8c59c64ccf0dd7753467b4c0f0bcf5f4b49c5bf0;>8c59c64) Documentation Annotate all Option factory methods with their Nullability bounds (https://github-redirect.dependabot.com/googleapis/java-storage/issues/1775;>#1775) (https://github.com/googleapis/java-storage/commit/3b8d137a113376d7dac9010b9207d435df2622f7;>3b8d137) Changelog Sourced from https://github.com/googleapis/java-storage/blob/main/CHANGELOG.md;>google-cloud-storage's changelog. https://github.com/googleapis/java-storage/compare/v2.15.0...v2.15.1;>2.15.1 (2022-11-17) Bug Fixes Disable REGAPIC transport in storage v2 (https://github-redirect.dependabot.com/googleapis/java-storage/issues/1762;>#1762) (https://github.com/googleapis/java-storage/commit/13d630e7ce89273c292acca7a7e048218ece4182;>13d630e) Update GrpcStorageImpl#get(BlobId) to return null on 404 (https://github-redirect.dependabot.com/googleapis/java-storage/issues/1772;>#1772) (https://github.com/googleapis/java-storage/commit/8c59c64ccf0dd7753467b4c0f0bcf5f4b49c5bf0;>8c59c64) Documentation Annotate all Option factory methods with their Nullability bounds (https://github-redirect.dependabot.com/googleapis/java-storage/issues/1775;>#1775) (https://github.com/googleapis/java-storage/commit/3b8d137a113376d7dac9010b9207d435df2622f7;>3b8d137) Commits https://github.com/googleapis/java-storage/commit/bfd48a1b5542ff28ffa337eba883c4ca6c3b0aad;>bfd48a1 chore(main): release 2.15.1 (https://github-redirect.dependabot.com/googleapis/java-storage/issues/1765;>#1765) https://github.com/googleapis/java-storage/commit/3b8d137a113376d7dac9010b9207d435df2622f7;>3b8d137 docs: annotate all Option factory methods with their Nullability bounds (https://github-redirect.dependabot.com/googleapis/java-storage/issues/1775;>#1775) https://github.com/googleapis/java-storage/commit/ba49f9d903d1c68f2a67ea56489fc64907d7d31d;>ba49f9d test(deps): update kms.version to v0.100.0 (https://github-redirect.dependabot.com/googleapis/java-storage/issues/1774;>#1774) https://github.com/googleapis/java-storage/commit/8c59c64ccf0dd7753467b4c0f0bcf5f4b49c5bf0;>8c59c64 fix: update GrpcStorageImpl#get(BlobId) to return null on 404 (https://github-redirect.dependabot.com/googleapis/java-storage/issues/1772;>#1772) https://github.com/googleapis/java-storage/commit/2770a38409e89f4f291ebf9ef23db0def0458b02;>2770a38 test(deps): update dependency org.mockito:mockito-core to v4.9.0 (https://github-redirect.dependabot.com/googleapis/java-storage/issues/1773;>#1773) https://github.com/googleapis/java-storage/commit/45b2b38c3850da1795a7fbd33e0560b949cb7810;>45b2b38 chore: use gcp-docuploader 0.6.3 (https://github-redirect.dependabot.com/googleapis/java-storage/issues/1708;>#1708) (https://github-redirect.dependabot.com/googleapis/java-storage/issues/1769;>#1769) https://github.com/googleapis/java-storage/commit/e0efa85c3cc7a0a092ab96a13f121b2d0e553c38;>e0efa85 test(deps): update dependency com.google.cloud:google-cloud-pubsub to v1.120 https://github.com/googleapis/java-storage/commit/feb9f06d7031915ce50a609f99a4d885e2b21f34;>feb9f06 test(deps): update dependency com.google.api.grpc:proto-google-cloud-pubsub-v... https://github.com/googleapis/java-storage/commit/b05ee42b24bb8b18b7cfcfd921a6a4f70d930ad2;>b05ee42 test(deps): update testbench version to v0.32.0 (https://github-redirect.dependabot.com/googleapis/java-storage/issues/1768;>#1768) https://github.com/googleapis/java-storage/commit/8ea8131d17eba29859518da7199bbd03019d0644;>8ea8131 chore: update google-auth to 2.14.1 (https://github-redirect.dependabot.com/googleapis/java-storage/issues/1703;>#1703) (https://github-redirect.dependabot.com/googleapis/java-storage/issues/1767;>#1767) Additional commits viewable in https://github.com/googleapis/java-storage/compare/v2.15.0...v2.15.1;>compare view [![Dependabot compatibility
[GitHub] [tika] dependabot[bot] opened a new pull request, #805: Bump sqlite-jdbc from 3.39.4.0 to 3.39.4.1
dependabot[bot] opened a new pull request, #805: URL: https://github.com/apache/tika/pull/805 Bumps [sqlite-jdbc](https://github.com/xerial/sqlite-jdbc) from 3.39.4.0 to 3.39.4.1. Release notes Sourced from https://github.com/xerial/sqlite-jdbc/releases;>sqlite-jdbc's releases. Release 3.39.4.1 Changelog Fixes jdbc: don't check if ResultSet is open in markCol (https://github.com/xerial/sqlite-jdbc/commits/6d6f756;>6d6f756) jdbc: throw SQLException instead of IllegalStateException (https://github.com/xerial/sqlite-jdbc/commits/4bfb174;>4bfb174) jdbc: properly handle updateCount for PreparedStatement (https://github.com/xerial/sqlite-jdbc/commits/6a910b9;>6a910b9) jdbc: don't close ResultSet when last row is passed (https://github.com/xerial/sqlite-jdbc/commits/a21229d;>a21229d) jdbc: properly reset Statement between reuse (https://github.com/xerial/sqlite-jdbc/commits/f497c43;>f497c43) Build fix boolean conditions, once more (https://github.com/xerial/sqlite-jdbc/commits/f11b824;>f11b824) fix boolean conditions (https://github.com/xerial/sqlite-jdbc/commits/857ed4c;>857ed4c) print event inputs (https://github.com/xerial/sqlite-jdbc/commits/83dbe02;>83dbe02) add failing tests for PreparedStatement getMetaData before execution (https://github.com/xerial/sqlite-jdbc/commits/6c95a88;>6c95a88) add failing tests for PreparedStatement getMoreResults and getUpdateCount (https://github.com/xerial/sqlite-jdbc/commits/98f00d3;>98f00d3) polish (https://github.com/xerial/sqlite-jdbc/commits/87c4601;>87c4601) replace deprecated set-output usage (https://github.com/xerial/sqlite-jdbc/commits/7ee209c;>7ee209c) add a release flag on CI workflow dispatch (https://github.com/xerial/sqlite-jdbc/commits/f9e5e7f;>f9e5e7f) add failing tests when getting ResultSet metadata past last row (https://github.com/xerial/sqlite-jdbc/commits/64771ef;>64771ef) add failing tests when reusing statements (https://github.com/xerial/sqlite-jdbc/commits/267e80b;>267e80b) deps: bump andymckay/cancel-action from 0.2 to 0.3 (https://github.com/xerial/sqlite-jdbc/commits/67b5899;>67b5899) fix attach-javadoc failing with release profile (https://github.com/xerial/sqlite-jdbc/commits/9d3e2ca;>9d3e2ca) change jreleaser's changelog format (https://github.com/xerial/sqlite-jdbc/commits/4896a15;>4896a15) multi-release JAR with module-info.java (https://github.com/xerial/sqlite-jdbc/commits/5bf7566;>5bf7566) Documentation update release process (https://github.com/xerial/sqlite-jdbc/commits/d91948e;>d91948e) Contributors We'd like to thank the following people for their contributions: Gauthier, Gauthier Roebroeck, GitHub, Petr Hadraba, dependabot[bot], github-actions Commits https://github.com/xerial/sqlite-jdbc/commit/0be1e803da08fb367b80a8ebb42e3809755100db;>0be1e80 chore(release): 3.39.4.1 [skip ci] https://github.com/xerial/sqlite-jdbc/commit/f11b82406e196b2a07f33431369a725ed40ea236;>f11b824 ci: fix boolean conditions, once more https://github.com/xerial/sqlite-jdbc/commit/857ed4cb8a99a6553f66be8e502e6f8a29f11749;>857ed4c ci: fix boolean conditions https://github.com/xerial/sqlite-jdbc/commit/83dbe025a8f8f1e4241904aadb4f5f3348527e91;>83dbe02 ci: print event inputs https://github.com/xerial/sqlite-jdbc/commit/6d6f756e9fd97f0f2c8e9d18c9b91ebbd8b52d7c;>6d6f756 fix(jdbc): don't check if ResultSet is open in markCol https://github.com/xerial/sqlite-jdbc/commit/4bfb174485d5ee49c18256451c8584049b7bc0d5;>4bfb174 fix(jdbc): throw SQLException instead of IllegalStateException https://github.com/xerial/sqlite-jdbc/commit/6c95a8868658ea0e8eb511700d09f9a7e1bab815;>6c95a88 test: add failing tests for PreparedStatement getMetaData before execution https://github.com/xerial/sqlite-jdbc/commit/6a910b93d9da0ad62b51a75e038dd31a1b5b247a;>6a910b9 fix(jdbc): properly handle updateCount for PreparedStatement https://github.com/xerial/sqlite-jdbc/commit/98f00d3d658f6322927e8fd14b8d7cd50c1377ff;>98f00d3 test: add failing tests for PreparedStatement getMoreResults and getUpdateCount https://github.com/xerial/sqlite-jdbc/commit/87c4601c0ade9547ac6fdab22572898741cb17d3;>87c4601 test: polish Additional commits viewable in https://github.com/xerial/sqlite-jdbc/compare/3.39.4.0...3.39.4.1;>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) ---
[GitHub] [tika] dependabot[bot] opened a new pull request, #804: Bump aws.version from 1.12.344 to 1.12.345
dependabot[bot] opened a new pull request, #804: URL: https://github.com/apache/tika/pull/804 Bumps `aws.version` from 1.12.344 to 1.12.345. Updates `aws-java-sdk-s3` from 1.12.344 to 1.12.345 Changelog Sourced from https://github.com/aws/aws-sdk-java/blob/master/CHANGELOG.md;>aws-java-sdk-s3's changelog. 1.12.345 2022-11-17 AWS Amplify Features Adds a new value (WEB_COMPUTE) to the Platform enum that allows customers to create Amplify Apps with Server-Side Rendering support. AWS AppSync Features This release introduces the APPSYNC_JS runtime, and adds support for JavaScript in AppSync functions and AppSync pipeline resolvers. AWS Database Migration Service Features Adds support for Internet Protocol Version 6 (IPv6) on DMS Replication Instances AWS Lambda Features Add Node 18 (nodejs18.x) support to AWS Lambda. AWS S3 Control Features Added 34 new S3 Storage Lens metrics to support additional customer use cases. AWS Secrets Manager Features Documentation updates for Secrets Manager. AWS Security Token Service Features Documentation updates for AWS Security Token Service. AWS SecurityHub Features Added SourceLayerArn and SourceLayerHash field for security findings. Updated AwsLambdaFunction Resource detail AWS Service Catalog App Registry Features This release adds support for tagged resource associations, which allows you to associate a group of resources with a defined resource tag key and value to the application. Amazon Appflow Features AppFlow simplifies the preparation and cataloging of SaaS data into the AWS Glue Data Catalog where your data can be discovered and accessed by AWS analytics and ML services. AppFlow now also supports data field partitioning and file size optimization to improve query performance and reduce cost. Amazon Elastic Compute Cloud Features This release adds a new optional parameter privateIpAddress for the CreateNatGateway API. PrivateIPAddress will allow customers to select a custom Private IPv4 address instead of having it be auto-assigned. Amazon Interactive Video Service Chat Features Adds LoggingConfiguration APIs for IVS Chat - a feature that allows customers to store and record sent messages in a chat room to S3 buckets, CloudWatch logs, or Kinesis firehose. Amazon Personalize ... (truncated) Commits https://github.com/aws/aws-sdk-java/commit/7e29a59064f4779fe45e0b287878cd7ddc85ea87;>7e29a59 AWS SDK for Java 1.12.345 https://github.com/aws/aws-sdk-java/commit/e0ca962c573b5815d80d3f089a07c7e7f74326b5;>e0ca962 Update GitHub version number to 1.12.345-SNAPSHOT See full diff in https://github.com/aws/aws-sdk-java/compare/1.12.344...1.12.345;>compare view Updates `aws-java-sdk-transcribe` from 1.12.344 to 1.12.345 Changelog Sourced from https://github.com/aws/aws-sdk-java/blob/master/CHANGELOG.md;>aws-java-sdk-transcribe's changelog. 1.12.345 2022-11-17 AWS Amplify Features Adds a new value (WEB_COMPUTE) to the Platform enum that allows customers to create Amplify Apps with Server-Side Rendering support. AWS AppSync Features This release introduces the APPSYNC_JS runtime, and adds support for JavaScript in AppSync functions and AppSync pipeline resolvers. AWS Database Migration Service Features Adds support for Internet Protocol Version 6 (IPv6) on DMS Replication Instances AWS Lambda Features Add Node 18 (nodejs18.x) support to AWS Lambda. AWS S3 Control Features Added 34 new S3 Storage Lens metrics to support additional customer use cases. AWS Secrets Manager Features Documentation updates for Secrets Manager. AWS Security Token Service Features Documentation updates for AWS Security Token Service. AWS SecurityHub Features Added SourceLayerArn and SourceLayerHash field for security findings. Updated AwsLambdaFunction Resource detail AWS Service Catalog App Registry Features This release adds support for tagged resource associations, which allows you to associate a group of resources with a defined resource tag key and value to the application. Amazon Appflow Features AppFlow simplifies the preparation and cataloging of SaaS data into the AWS Glue Data Catalog where your data can be discovered and accessed by AWS analytics and ML services.
[jira] [Commented] (TIKA-3308) SVG file without xml declaration tag is detected as text/plain
[
https://issues.apache.org/jira/browse/TIKA-3308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17635630#comment-17635630
]
Tsuyoshi Yoshizawa commented on TIKA-3308:
--
I have the same issue.
> Checking for {{http://www.w3.org/2000/svg"}} with a decent
> priority should be fine, but I'm not sure we'd want to look for just {{ SVG file without xml declaration tag is detected as text/plain
> --
>
> Key: TIKA-3308
> URL: https://issues.apache.org/jira/browse/TIKA-3308
> Project: Tika
> Issue Type: Bug
> Components: mime
>Affects Versions: 1.25
>Reporter: Anas Hammani
>Priority: Minor
> Attachments: logo-luma.svg
>
>
> The SVG file attached to the issue is interpreted as *text/plain* by
> {code:java}
> tika.detect(filePath){code}
>
> If I add
> {code:java}
> {code}
> at the beginning of the file, then tika detects it as "image/svg+xml"
>
> When i read the documentation i see that xml is not necessary for a file to
> be well-formed
> [https://www.w3.org/TR/REC-xml/#sec-prolog-dtd]
>
> It will be great if tika can detect a file as a SVG without the prolog
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (TIKA-3932) New repeatable test failures on Solr integration tests for Solr 6 on macosx aarch
[ https://issues.apache.org/jira/browse/TIKA-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17635540#comment-17635540 ] Hudson commented on TIKA-3932: -- SUCCESS: Integrated in Jenkins build Tika » tika-main-jdk8 #925 (See [https://ci-builds.apache.org/job/Tika/job/tika-main-jdk8/925/]) TIKA-3932 -- temporary workaround :( (tallison: [https://github.com/apache/tika/commit/bc158d59660f8588868f8687a87e389d8079b706]) * (edit) tika-integration-tests/tika-pipes-kafka-integration-tests/src/test/java/org/apache/tika/pipes/kafka/tests/TikaPipesKafkaTest.java * (edit) tika-integration-tests/tika-pipes-solr-integration-tests/src/test/java/org/apache/tika/pipes/solr/tests/TikaPipesSolr6Test.java > New repeatable test failures on Solr integration tests for Solr 6 on macosx > aarch > - > > Key: TIKA-3932 > URL: https://issues.apache.org/jira/browse/TIKA-3932 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Priority: Trivial > > Docker has been a bit on and off since I got an m1 mac so I haven't been > running the tests that require Docker much. > I just noticed a few days ago that I'm consistently getting a failed test on > the SolrIntegration test for Solr 6. Everything else appears to be working. > I'm not seeing this test failure on ubuntu, and our CI/CD is not picking it > up on their OS. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (TIKA-3931) Add a jdbc pipesreporter
[ https://issues.apache.org/jira/browse/TIKA-3931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17635541#comment-17635541 ] Hudson commented on TIKA-3931: -- SUCCESS: Integrated in Jenkins build Tika » tika-main-jdk8 #925 (See [https://ci-builds.apache.org/job/Tika/job/tika-main-jdk8/925/]) TIKA-3931 (#803) (github: [https://github.com/apache/tika/commit/f846009d6e9b4789f8057b1b27fde7caa8d4cbda]) * (add) tika-pipes/tika-pipes-reporters/tika-pipes-reporter-jdbc/src/test/resources/tika-config-includes.xml * (edit) tika-pipes/tika-pipes-reporters/pom.xml * (edit) tika-bom/pom.xml * (edit) tika-core/src/main/java/org/apache/tika/pipes/PipesReporter.java * (add) tika-core/src/main/java/org/apache/tika/pipes/PipesReporterBase.java * (add) tika-pipes/tika-pipes-reporters/tika-pipes-reporter-jdbc/src/test/java/org/apache/tika/pipes/reporters/jdbc/TestJDBCPipesReporter.java * (add) tika-pipes/tika-pipes-reporters/tika-pipes-reporter-jdbc/pom.xml * (edit) CHANGES.txt * (add) tika-pipes/tika-pipes-reporters/tika-pipes-reporter-jdbc/src/main/java/org/apache/tika/pipes/reporters/jdbc/JDBCPipesReporter.java * (add) tika-pipes/tika-pipes-reporters/tika-pipes-reporter-jdbc/src/test/resources/tika-config-excludes.xml > Add a jdbc pipesreporter > > > Key: TIKA-3931 > URL: https://issues.apache.org/jira/browse/TIKA-3931 > Project: Tika > Issue Type: Task > Components: tika-pipes >Reporter: Tim Allison >Priority: Major > Fix For: 2.6.1 > > > It would be useful to have a jdbc pipes reporter to store status for each > file. We should let users configure table name and which status updates > they'd like to have reported via includes set or excludes set. We can also > allow users to set the batch update size. > As with all PipesReporters, this will need to be thread safe. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (TIKA-3932) New repeatable test failures on Solr integration tests for Solr 6 on macosx aarch
[ https://issues.apache.org/jira/browse/TIKA-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17635525#comment-17635525 ] Tim Allison commented on TIKA-3932: --- I tried reverting to an older version of testcontainers, and I tried increasing resources available to Docker. Neither of those solved the problem. :( > New repeatable test failures on Solr integration tests for Solr 6 on macosx > aarch > - > > Key: TIKA-3932 > URL: https://issues.apache.org/jira/browse/TIKA-3932 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Priority: Trivial > > Docker has been a bit on and off since I got an m1 mac so I haven't been > running the tests that require Docker much. > I just noticed a few days ago that I'm consistently getting a failed test on > the SolrIntegration test for Solr 6. Everything else appears to be working. > I'm not seeing this test failure on ubuntu, and our CI/CD is not picking it > up on their OS. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (TIKA-3932) New repeatable test failures on Solr integration tests for Solr 6 on macosx aarch
[ https://issues.apache.org/jira/browse/TIKA-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17635519#comment-17635519 ] Tim Allison commented on TIKA-3932: --- I've turned these off as a temporary workaround. Once I figure out what caused these problems...and if there's a solution, I'll try to turn them back on. Sorry for this... > New repeatable test failures on Solr integration tests for Solr 6 on macosx > aarch > - > > Key: TIKA-3932 > URL: https://issues.apache.org/jira/browse/TIKA-3932 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Priority: Trivial > > Docker has been a bit on and off since I got an m1 mac so I haven't been > running the tests that require Docker much. > I just noticed a few days ago that I'm consistently getting a failed test on > the SolrIntegration test for Solr 6. Everything else appears to be working. > I'm not seeing this test failure on ubuntu, and our CI/CD is not picking it > up on their OS. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (TIKA-3932) New repeatable test failures on Solr integration tests for Solr 6 on macosx aarch
[ https://issues.apache.org/jira/browse/TIKA-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17635517#comment-17635517 ] Tim Allison commented on TIKA-3932: --- Turns out my laptop doesn't like the kafka test either: Failures: [ERROR] TikaPipesKafkaTest.testKafkaPipeIteratorAndEmitter:189 Timed out after 2 minutes waiting for the emitted docs ==> expected: but was: [INFO] [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0 > New repeatable test failures on Solr integration tests for Solr 6 on macosx > aarch > - > > Key: TIKA-3932 > URL: https://issues.apache.org/jira/browse/TIKA-3932 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Priority: Trivial > > Docker has been a bit on and off since I got an m1 mac so I haven't been > running the tests that require Docker much. > I just noticed a few days ago that I'm consistently getting a failed test on > the SolrIntegration test for Solr 6. Everything else appears to be working. > I'm not seeing this test failure on ubuntu, and our CI/CD is not picking it > up on their OS. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (TIKA-3932) New repeatable test failures on Solr integration tests for Solr 6 on macosx aarch
[ https://issues.apache.org/jira/browse/TIKA-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17635506#comment-17635506 ] Tim Allison commented on TIKA-3932: --- [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 4.654 s <<< FAILURE! - in org.apache.tika.pipes.solr.tests.TikaPipesSolr6Test [ERROR] org.apache.tika.pipes.solr.tests.TikaPipesSolr6Test.testPipesIteratorWithSolrUrls Time elapsed: 2.221 s <<< ERROR! org.apache.http.NoHttpResponseException: The target server failed to respond at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:141) at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:56) at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:259) at org.apache.http.impl.DefaultBHttpClientConnection.receiveResponseHeader(DefaultBHttpClientConnection.java:163) > New repeatable test failures on Solr integration tests for Solr 6 on macosx > aarch > - > > Key: TIKA-3932 > URL: https://issues.apache.org/jira/browse/TIKA-3932 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Priority: Trivial > > Docker has been a bit on and off since I got an m1 mac so I haven't been > running the tests that require Docker much. > I just noticed a few days ago that I'm consistently getting a failed test on > the SolrIntegration test for Solr 6. Everything else appears to be working. > I'm not seeing this test failure on ubuntu, and our CI/CD is not picking it > up on their OS. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (TIKA-3931) Add a jdbc pipesreporter
[ https://issues.apache.org/jira/browse/TIKA-3931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Allison resolved TIKA-3931. --- Fix Version/s: 2.6.1 Resolution: Fixed > Add a jdbc pipesreporter > > > Key: TIKA-3931 > URL: https://issues.apache.org/jira/browse/TIKA-3931 > Project: Tika > Issue Type: Task > Components: tika-pipes >Reporter: Tim Allison >Priority: Major > Fix For: 2.6.1 > > > It would be useful to have a jdbc pipes reporter to store status for each > file. We should let users configure table name and which status updates > they'd like to have reported via includes set or excludes set. We can also > allow users to set the batch update size. > As with all PipesReporters, this will need to be thread safe. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (TIKA-3931) Add a jdbc pipesreporter
[ https://issues.apache.org/jira/browse/TIKA-3931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17635504#comment-17635504 ] ASF GitHub Bot commented on TIKA-3931: -- tballison merged PR #803: URL: https://github.com/apache/tika/pull/803 > Add a jdbc pipesreporter > > > Key: TIKA-3931 > URL: https://issues.apache.org/jira/browse/TIKA-3931 > Project: Tika > Issue Type: Task > Components: tika-pipes >Reporter: Tim Allison >Priority: Major > > It would be useful to have a jdbc pipes reporter to store status for each > file. We should let users configure table name and which status updates > they'd like to have reported via includes set or excludes set. We can also > allow users to set the batch update size. > As with all PipesReporters, this will need to be thread safe. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [tika] tballison merged pull request #803: TIKA-3931
tballison merged PR #803: URL: https://github.com/apache/tika/pull/803 -- 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] [Updated] (TIKA-3735) Require Java 11 for 2.x at some point
[ https://issues.apache.org/jira/browse/TIKA-3735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Allison updated TIKA-3735: -- Description: This follows on from discussion we had on the user/dev list for when we want to require Java 11. I think the consensus was: wait until we have to. The following libraries require > Java 8 at the moment. I don't think updating any of these is critical, but I do want to document where we're stuck. We can modify/edit this list as necessary: * Apache OpenNLP 2.0.0 requires Java 11. * DL4J 1.0.0-M2.1 - datavec-data-image-1.0.0-M2.1.jar requires Java 11 * Lucene 9.x -- used in tika-eval * icu4j -- we can't upgrade past 62.2 (April 2019) because that is the latest version that is compatible with Lucene 8.11.1 (https://github.com/apache/tika/pull/587) * mime4j -- the last 2 (or three?) releases have been accidentally built with Java 9 without the correct release=8. This should be fixed in the next release. * Fakeload * [checkstyle|https://mail.google.com/mail/u/0/#label/lists%2Ftika/WhctKKXXHvjnJRRdBSwLbKkDkXQtRnWGDhblVMQQZhjsDGrFpRMRQJJrZSdskrNCqcmTtjL] * errorprone requires Java 11 for the build (doesn't mean we can't target 8) was: This follows on from discussion we had on the user/dev list for when we want to require Java 11. I think the consensus was: wait until we have to. The following libraries require > Java 8 at the moment. I don't think updating any of these is critical, but I do want to document where we're stuck. We can modify/edit this list as necessary: * Apache OpenNLP 2.0.0 requires Java 11. * DL4J 1.0.0-M2.1 - datavec-data-image-1.0.0-M2.1.jar requires Java 11 * Lucene 9.x -- used in tika-eval * icu4j -- we can't upgrade past 62.2 (April 2019) because that is the latest version that is compatible with Lucene 8.11.1 (https://github.com/apache/tika/pull/587) * mime4j -- the last 2 (or three?) releases have been accidentally built with Java 9 without the correct release=8. This should be fixed in the next release. * Fakeload * [checkstyle|https://mail.google.com/mail/u/0/#label/lists%2Ftika/WhctKKXXHvjnJRRdBSwLbKkDkXQtRnWGDhblVMQQZhjsDGrFpRMRQJJrZSdskrNCqcmTtjL] > Require Java 11 for 2.x at some point > - > > Key: TIKA-3735 > URL: https://issues.apache.org/jira/browse/TIKA-3735 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Priority: Major > > This follows on from discussion we had on the user/dev list for when we want > to require Java 11. I think the consensus was: wait until we have to. > The following libraries require > Java 8 at the moment. I don't think > updating any of these is critical, but I do want to document where we're > stuck. > We can modify/edit this list as necessary: > * Apache OpenNLP 2.0.0 requires Java 11. > * DL4J 1.0.0-M2.1 - datavec-data-image-1.0.0-M2.1.jar requires Java 11 > * Lucene 9.x -- used in tika-eval > * icu4j -- we can't upgrade past 62.2 (April 2019) because that is the latest > version that is compatible with Lucene 8.11.1 > (https://github.com/apache/tika/pull/587) > * mime4j -- the last 2 (or three?) releases have been accidentally built with > Java 9 without the correct release=8. This should be fixed in the next > release. > * Fakeload > * > [checkstyle|https://mail.google.com/mail/u/0/#label/lists%2Ftika/WhctKKXXHvjnJRRdBSwLbKkDkXQtRnWGDhblVMQQZhjsDGrFpRMRQJJrZSdskrNCqcmTtjL] > * errorprone requires Java 11 for the build (doesn't mean we can't target 8) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (TIKA-3932) New repeatable test failures on Solr integration tests for Solr 6 on macosx aarch
Tim Allison created TIKA-3932: - Summary: New repeatable test failures on Solr integration tests for Solr 6 on macosx aarch Key: TIKA-3932 URL: https://issues.apache.org/jira/browse/TIKA-3932 Project: Tika Issue Type: Task Reporter: Tim Allison Docker has been a bit on and off since I got an m1 mac so I haven't been running the tests that require Docker much. I just noticed a few days ago that I'm consistently getting a failed test on the SolrIntegration test for Solr 6. Everything else appears to be working. I'm not seeing this test failure on ubuntu, and our CI/CD is not picking it up on their OS. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (TIKA-3932) New repeatable test failures on Solr integration tests for Solr 6 on macosx aarch
[ https://issues.apache.org/jira/browse/TIKA-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Allison updated TIKA-3932: -- Priority: Trivial (was: Minor) > New repeatable test failures on Solr integration tests for Solr 6 on macosx > aarch > - > > Key: TIKA-3932 > URL: https://issues.apache.org/jira/browse/TIKA-3932 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Priority: Trivial > > Docker has been a bit on and off since I got an m1 mac so I haven't been > running the tests that require Docker much. > I just noticed a few days ago that I'm consistently getting a failed test on > the SolrIntegration test for Solr 6. Everything else appears to be working. > I'm not seeing this test failure on ubuntu, and our CI/CD is not picking it > up on their OS. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (TIKA-3931) Add a jdbc pipesreporter
[ https://issues.apache.org/jira/browse/TIKA-3931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17635488#comment-17635488 ] ASF GitHub Bot commented on TIKA-3931: -- tballison opened a new pull request, #803: URL: https://github.com/apache/tika/pull/803 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 a jdbc pipesreporter > > > Key: TIKA-3931 > URL: https://issues.apache.org/jira/browse/TIKA-3931 > Project: Tika > Issue Type: Task > Components: tika-pipes >Reporter: Tim Allison >Priority: Major > > It would be useful to have a jdbc pipes reporter to store status for each > file. We should let users configure table name and which status updates > they'd like to have reported via includes set or excludes set. We can also > allow users to set the batch update size. > As with all PipesReporters, this will need to be thread safe. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [tika] tballison opened a new pull request, #803: TIKA-3931
tballison opened a new pull request, #803: URL: https://github.com/apache/tika/pull/803 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] [Commented] (TIKA-3929) Add crash as an option in PipesReporter
[ https://issues.apache.org/jira/browse/TIKA-3929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17635460#comment-17635460 ] Hudson commented on TIKA-3929: -- SUCCESS: Integrated in Jenkins build Tika » tika-main-jdk8 #924 (See [https://ci-builds.apache.org/job/Tika/job/tika-main-jdk8/924/]) TIKA-3929 -- add a crash option for PipesReporter (tallison: [https://github.com/apache/tika/commit/46901964b2221fd882b2c550e784f766f2b726bd]) * (edit) tika-pipes/tika-pipes-reporters/tika-pipes-reporter-fs-status/src/main/java/org/apache/tika/pipes/reporters/fs/FileSystemStatusReporter.java * (edit) tika-core/src/test/java/org/apache/tika/pipes/async/MockReporter.java * (edit) tika-core/src/main/java/org/apache/tika/pipes/CompositePipesReporter.java * (edit) tika-core/src/main/java/org/apache/tika/pipes/async/AsyncProcessor.java * (edit) tika-core/src/main/java/org/apache/tika/pipes/LoggingPipesReporter.java * (edit) tika-core/src/main/java/org/apache/tika/pipes/PipesReporter.java * (edit) CHANGES.txt * (edit) tika-pipes/tika-pipes-reporters/tika-pipes-reporter-opensearch/src/main/java/org/apache/tika/pipes/reporters/opensearch/OpenSearchPipesReporter.java * (edit) tika-core/src/main/java/org/apache/tika/pipes/async/AsyncStatus.java > Add crash as an option in PipesReporter > --- > > Key: TIKA-3929 > URL: https://issues.apache.org/jira/browse/TIKA-3929 > Project: Tika > Issue Type: Task > Components: tika-pipes >Reporter: Tim Allison >Priority: Minor > Fix For: 2.6.1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (TIKA-3930) Allow users to configure multivalued field strategy in jdbc emitter
[ https://issues.apache.org/jira/browse/TIKA-3930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17635461#comment-17635461 ] Hudson commented on TIKA-3930: -- SUCCESS: Integrated in Jenkins build Tika » tika-main-jdk8 #924 (See [https://ci-builds.apache.org/job/Tika/job/tika-main-jdk8/924/]) TIKA-3930 -- Add multivalued field strategy option in jdbc-emitter (tallison: [https://github.com/apache/tika/commit/7eb1a422597ebe7089dcbd6c55719390e8beca8c]) * (edit) tika-pipes/tika-fetchers/pom.xml * (edit) tika-pipes/pom.xml * (add) tika-pipes/tika-emitters/tika-emitter-jdbc/src/test/resources/configs/tika-config-jdbc-emitter-multivalued.xml * (edit) CHANGES.txt * (edit) tika-pipes/tika-emitters/tika-emitter-jdbc/src/main/java/org/apache/tika/pipes/emitter/jdbc/JDBCEmitter.java * (edit) tika-pipes/tika-emitters/tika-emitter-jdbc/src/test/java/org/apache/tika/pipes/emitter/jdbc/JDBCEmitterTest.java > Allow users to configure multivalued field strategy in jdbc emitter > --- > > Key: TIKA-3930 > URL: https://issues.apache.org/jira/browse/TIKA-3930 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Priority: Minor > Fix For: 2.6.1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (TIKA-3931) Add a jdbc pipesreporter
[ https://issues.apache.org/jira/browse/TIKA-3931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Allison updated TIKA-3931: -- Description: It would be useful to have a jdbc pipes reporter to store status for each file. We should let users configure table name and which status updates they'd like to have reported via includes set or excludes set. We can also allow users to set the batch update size. As with all PipesReporters, this will need to be thread safe. > Add a jdbc pipesreporter > > > Key: TIKA-3931 > URL: https://issues.apache.org/jira/browse/TIKA-3931 > Project: Tika > Issue Type: Task > Components: tika-pipes >Reporter: Tim Allison >Priority: Major > > It would be useful to have a jdbc pipes reporter to store status for each > file. We should let users configure table name and which status updates > they'd like to have reported via includes set or excludes set. We can also > allow users to set the batch update size. > As with all PipesReporters, this will need to be thread safe. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (TIKA-3931) Add a jdbc pipesreporter
Tim Allison created TIKA-3931: - Summary: Add a jdbc pipesreporter Key: TIKA-3931 URL: https://issues.apache.org/jira/browse/TIKA-3931 Project: Tika Issue Type: Task Components: tika-pipes Reporter: Tim Allison -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (TIKA-3930) Allow users to configure multivalued field strategy in jdbc emitter
[ https://issues.apache.org/jira/browse/TIKA-3930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Allison resolved TIKA-3930. --- Fix Version/s: 2.6.1 Resolution: Fixed > Allow users to configure multivalued field strategy in jdbc emitter > --- > > Key: TIKA-3930 > URL: https://issues.apache.org/jira/browse/TIKA-3930 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Priority: Minor > Fix For: 2.6.1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (TIKA-3930) Allow users to configure multivalued field strategy in jdbc emitter
Tim Allison created TIKA-3930: - Summary: Allow users to configure multivalued field strategy in jdbc emitter Key: TIKA-3930 URL: https://issues.apache.org/jira/browse/TIKA-3930 Project: Tika Issue Type: Task Reporter: Tim Allison -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (TIKA-3917) General upgrades for 2.6.1
[ https://issues.apache.org/jira/browse/TIKA-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17635233#comment-17635233 ] Hudson commented on TIKA-3917: -- SUCCESS: Integrated in Jenkins build Tika » tika-main-jdk8 #923 (See [https://ci-builds.apache.org/job/Tika/job/tika-main-jdk8/923/]) TIKA-3917: update spring (tilman: [https://github.com/apache/tika/commit/0ccc3bf5ebddc864072ba94d4321a1985062fa06]) * (edit) tika-parent/pom.xml > General upgrades for 2.6.1 > -- > > Key: TIKA-3917 > URL: https://issues.apache.org/jira/browse/TIKA-3917 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
