[jira] [Commented] (TIKA-3948) Require Java 11 in 3.x
[
https://issues.apache.org/jira/browse/TIKA-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17758637#comment-17758637
]
Maxim Solodovnik commented on TIKA-3948:
Sorry for delay :(
Did quick check:
check {{javax}} in result of {{mvn dependency:tree}}
Direct dependencies
{{bcmail-jdk18on -> bcjmail-jdk18on}}
{{jaxb-runtime2 -> jaxb-runtime4}}
{{javax.annotation:javax.annotation-api ->
jakarta.annotation:jakarta.annotation-api}}
{{javax.ws.rs:javax.ws.rs-api -> jakarta.ws.rs:jakarta.ws.rs-api}}
{{javax.inject:javax.inject -> jakarta.inject:jakarta.inject-api}}
{{javax.activation:activation -> jakarta.activation:jakarta.activation-api}}
Transitive dependencies
{{javax.annotation:javax.annotation-api ->
jakarta.annotation:jakarta.annotation-api}}
{{javax.inject:javax.inject -> jakarta.inject:jakarta.inject-api}}
{{javax.servlet:javax.servlet-api -> jakarta.servlet:jakarta.servlet-api}}
{{javax.ws.rs:javax.ws.rs-api -> jakarta.ws.rs:jakarta.ws.rs-api}}
{{javax.validation:validation-api -> jakarta.validation:jakarta.validation-api}}
Grep sources using: {{find . -name *.java | while read JAVA; do grep -H javax
$JAVA; done}}
{{javax.xml.transform -> jakarta.xml.transform}}
{{javax.ws.rs -> jakarta.ws.rs}}
Not sure if this list complete or not :)
Shall I create PR with above changes? :)
> Require Java 11 in 3.x
> --
>
> Key: TIKA-3948
> URL: https://issues.apache.org/jira/browse/TIKA-3948
> Project: Tika
> Issue Type: Task
>Reporter: Tim Allison
>Priority: Major
> Labels: tika-3x
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[DISCUSS] 3.x?
All, What should we set as the goals and timeline for 3.x and the EOL for 2.x? At the moment, I don't have visions of much beyond requiring Java 11 in 3.x and bumping the dependencies that we've been stuck with because of Java 8. What do you think? Aim for initial 3.0.0 release by the end of September 2023, with EOL for 2.x September 2024? Best, Tim
[jira] [Commented] (TIKA-3948) Require Java 11 in 3.x
[ https://issues.apache.org/jira/browse/TIKA-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17758669#comment-17758669 ] Tim Allison commented on TIKA-3948: --- No apologies at all! I (re-)started a thread on what do we want in 3.x: https://lists.apache.org/thread/c330b12h1fvmq8x1099mgw3tfs0gcp6q The lazy part of me thinks we should probably create a 2x branch and then create a PR against main for 3x development at some point soon. Maybe leave a week for discussion on the above thread before we create the new branch and open a PR? > Require Java 11 in 3.x > -- > > Key: TIKA-3948 > URL: https://issues.apache.org/jira/browse/TIKA-3948 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Priority: Major > Labels: tika-3x > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [tika] tballison opened a new pull request, #1302: TIKA-4016
tballison opened a new pull request, #1302: URL: https://github.com/apache/tika/pull/1302 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-4016) Upgrade to PDFBox 2.0.28
[ https://issues.apache.org/jira/browse/TIKA-4016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17758682#comment-17758682 ] ASF GitHub Bot commented on TIKA-4016: -- tballison opened a new pull request, #1302: URL: https://github.com/apache/tika/pull/1302 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! > Upgrade to PDFBox 2.0.28 > > > Key: TIKA-4016 > URL: https://issues.apache.org/jira/browse/TIKA-4016 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Priority: Minor > Fix For: 2.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [tika] tballison closed pull request #1302: TIKA-4016
tballison closed pull request #1302: TIKA-4016 URL: https://github.com/apache/tika/pull/1302 -- 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-4016) Upgrade to PDFBox 2.0.28
[ https://issues.apache.org/jira/browse/TIKA-4016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17758686#comment-17758686 ] ASF GitHub Bot commented on TIKA-4016: -- tballison closed pull request #1302: TIKA-4016 URL: https://github.com/apache/tika/pull/1302 > Upgrade to PDFBox 2.0.28 > > > Key: TIKA-4016 > URL: https://issues.apache.org/jira/browse/TIKA-4016 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Priority: Minor > Fix For: 2.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [tika] tballison opened a new pull request, #1303: TIKA-4106
tballison opened a new pull request, #1303: URL: https://github.com/apache/tika/pull/1303 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-4016) Upgrade to PDFBox 2.0.28
[ https://issues.apache.org/jira/browse/TIKA-4016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17758689#comment-17758689 ] Tim Allison commented on TIKA-4016: --- Sorry for the noise. Wrong ticket number. :( > Upgrade to PDFBox 2.0.28 > > > Key: TIKA-4016 > URL: https://issues.apache.org/jira/browse/TIKA-4016 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Priority: Minor > Fix For: 2.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (TIKA-4106) Digesting and content length on embedded ole/zip/pdf files are not calculated
[ https://issues.apache.org/jira/browse/TIKA-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17758688#comment-17758688 ] ASF GitHub Bot commented on TIKA-4106: -- tballison opened a new pull request, #1303: URL: https://github.com/apache/tika/pull/1303 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! > Digesting and content length on embedded ole/zip/pdf files are not calculated > - > > Key: TIKA-4106 > URL: https://issues.apache.org/jira/browse/TIKA-4106 > Project: Tika > Issue Type: Improvement >Reporter: Tim Allison >Priority: Major > > We've currently put the digester on the parser. The problem is that some of > the detectors for some file formats open the full file and then put that > object in the openContainer of the TikaInputStream, which means that the > InputStream for those parsers that reuse the openContainer (created by the > detector) is never read. > > > The outcome of this is that embedded OLE2, Zip (in some circumstances) and > PDF(?) files are never digested nor are their stream lengths extracted. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (TIKA-4106) Digesting and content length on embedded ole/zip/pdf files are not calculated
[
https://issues.apache.org/jira/browse/TIKA-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17758692#comment-17758692
]
Tim Allison commented on TIKA-4106:
---
I looked into this a bit more. I _think_ we're ok in the items that I listed
above. I did find that if we don't set {{spoolToDisk}} to {{0}}, e.g. if we're
processing embedded file streams in memory, we often don't get the length of
the stream. So, I added length via the digester. The notion is that if people
care about lengths of embedded files, they'll probably also want digests of
embedded files and vice versa.
There are still some files where we miss digests when there's an exception in
the container file, but that's to be expected.
> Digesting and content length on embedded ole/zip/pdf files are not calculated
> -
>
> Key: TIKA-4106
> URL: https://issues.apache.org/jira/browse/TIKA-4106
> Project: Tika
> Issue Type: Improvement
>Reporter: Tim Allison
>Priority: Major
>
> We've currently put the digester on the parser. The problem is that some of
> the detectors for some file formats open the full file and then put that
> object in the openContainer of the TikaInputStream, which means that the
> InputStream for those parsers that reuse the openContainer (created by the
> detector) is never read.
>
>
> The outcome of this is that embedded OLE2, Zip (in some circumstances) and
> PDF(?) files are never digested nor are their stream lengths extracted.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [tika] tballison commented on pull request #1302: TIKA-4016
tballison commented on PR #1302: URL: https://github.com/apache/tika/pull/1302#issuecomment-1692199572 Sorry, wrong issue number on branch name. -- 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-4016) Upgrade to PDFBox 2.0.28
[ https://issues.apache.org/jira/browse/TIKA-4016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17758693#comment-17758693 ] ASF GitHub Bot commented on TIKA-4016: -- tballison commented on PR #1302: URL: https://github.com/apache/tika/pull/1302#issuecomment-1692199572 Sorry, wrong issue number on branch name. > Upgrade to PDFBox 2.0.28 > > > Key: TIKA-4016 > URL: https://issues.apache.org/jira/browse/TIKA-4016 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Priority: Minor > Fix For: 2.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [tika] tballison merged pull request #1303: TIKA-4106
tballison merged PR #1303: URL: https://github.com/apache/tika/pull/1303 -- 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-4106) Digesting and content length on embedded ole/zip/pdf files are not calculated
[ https://issues.apache.org/jira/browse/TIKA-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17758702#comment-17758702 ] ASF GitHub Bot commented on TIKA-4106: -- tballison merged PR #1303: URL: https://github.com/apache/tika/pull/1303 > Digesting and content length on embedded ole/zip/pdf files are not calculated > - > > Key: TIKA-4106 > URL: https://issues.apache.org/jira/browse/TIKA-4106 > Project: Tika > Issue Type: Improvement >Reporter: Tim Allison >Priority: Major > > We've currently put the digester on the parser. The problem is that some of > the detectors for some file formats open the full file and then put that > object in the openContainer of the TikaInputStream, which means that the > InputStream for those parsers that reuse the openContainer (created by the > detector) is never read. > > > The outcome of this is that embedded OLE2, Zip (in some circumstances) and > PDF(?) files are never digested nor are their stream lengths extracted. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (TIKA-4016) Upgrade to PDFBox 2.0.28
[ https://issues.apache.org/jira/browse/TIKA-4016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17758730#comment-17758730 ] Hudson commented on TIKA-4016: -- SUCCESS: Integrated in Jenkins build Tika » tika-main-jdk11 #1219 (See [https://ci-builds.apache.org/job/Tika/job/tika-main-jdk11/1219/]) TIKA-4016 -- add length in InputStreamDigester (#1303) (github: [https://github.com/apache/tika/commit/a2f1a19154ee0284195637ef0142c5d232ee309e]) * (edit) CHANGES.txt * (edit) tika-parsers/tika-parsers-standard/tika-parsers-standard-package/src/test/java/org/apache/tika/parser/DigestingParserTest.java * (edit) tika-core/src/main/java/org/apache/tika/parser/digest/InputStreamDigester.java > Upgrade to PDFBox 2.0.28 > > > Key: TIKA-4016 > URL: https://issues.apache.org/jira/browse/TIKA-4016 > Project: Tika > Issue Type: Task >Reporter: Tim Allison >Priority: Minor > Fix For: 2.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [DISCUSS] 3.x?
On 2023/08/24 16:33:54 Tim Allison wrote: > All, > > What should we set as the goals and timeline for 3.x and the EOL for 2.x? > > At the moment, I don't have visions of much beyond requiring Java 11 in > 3.x and bumping the dependencies that we've been stuck with because of Java > 8. What do you think? > > Aim for initial 3.0.0 release by the end of September 2023, with EOL for > 2.x September 2024? I doubt you can EOL 2.x in case you are planing to move to Jackarta IMO these 2 worlds will live in parallel much longer :( In case you are planing to have one branch maybe it worth to do something like this: https://issues.apache.org/jira/browse/JCR-4892 Not sure if it is possible for Tika ... :( > > Best, > >Tim >
[jira] [Comment Edited] (TIKA-3948) Require Java 11 in 3.x
[
https://issues.apache.org/jira/browse/TIKA-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17758637#comment-17758637
]
Maxim Solodovnik edited comment on TIKA-3948 at 8/25/23 2:32 AM:
-
Sorry for delay :(
Did quick check:
check {{javax}} in result of {{mvn dependency:tree}}
Direct dependencies
{{bcmail-jdk18on -> bcjmail-jdk18on}}
{{jaxb-runtime2 -> jaxb-runtime4}}
{{spring5 -> spring6}}
{{javax.annotation:javax.annotation-api ->
jakarta.annotation:jakarta.annotation-api}}
{{javax.ws.rs:javax.ws.rs-api -> jakarta.ws.rs:jakarta.ws.rs-api}}
{{javax.inject:javax.inject -> jakarta.inject:jakarta.inject-api}}
{{javax.activation:activation -> jakarta.activation:jakarta.activation-api}}
Transitive dependencies
{{javax.annotation:javax.annotation-api ->
jakarta.annotation:jakarta.annotation-api}}
{{javax.inject:javax.inject -> jakarta.inject:jakarta.inject-api}}
{{javax.servlet:javax.servlet-api -> jakarta.servlet:jakarta.servlet-api}}
{{javax.ws.rs:javax.ws.rs-api -> jakarta.ws.rs:jakarta.ws.rs-api}}
{{javax.validation:validation-api -> jakarta.validation:jakarta.validation-api}}
Grep sources using: {{find . -name *.java | while read JAVA; do grep -H javax
$JAVA; done}}
{{javax.xml.transform -> jakarta.xml.transform}}
{{javax.ws.rs -> jakarta.ws.rs}}
Not sure if this list complete or not :)
Shall I create PR with above changes? :)
was (Author: solomax):
Sorry for delay :(
Did quick check:
check {{javax}} in result of {{mvn dependency:tree}}
Direct dependencies
{{bcmail-jdk18on -> bcjmail-jdk18on}}
{{jaxb-runtime2 -> jaxb-runtime4}}
{{javax.annotation:javax.annotation-api ->
jakarta.annotation:jakarta.annotation-api}}
{{javax.ws.rs:javax.ws.rs-api -> jakarta.ws.rs:jakarta.ws.rs-api}}
{{javax.inject:javax.inject -> jakarta.inject:jakarta.inject-api}}
{{javax.activation:activation -> jakarta.activation:jakarta.activation-api}}
Transitive dependencies
{{javax.annotation:javax.annotation-api ->
jakarta.annotation:jakarta.annotation-api}}
{{javax.inject:javax.inject -> jakarta.inject:jakarta.inject-api}}
{{javax.servlet:javax.servlet-api -> jakarta.servlet:jakarta.servlet-api}}
{{javax.ws.rs:javax.ws.rs-api -> jakarta.ws.rs:jakarta.ws.rs-api}}
{{javax.validation:validation-api -> jakarta.validation:jakarta.validation-api}}
Grep sources using: {{find . -name *.java | while read JAVA; do grep -H javax
$JAVA; done}}
{{javax.xml.transform -> jakarta.xml.transform}}
{{javax.ws.rs -> jakarta.ws.rs}}
Not sure if this list complete or not :)
Shall I create PR with above changes? :)
> Require Java 11 in 3.x
> --
>
> Key: TIKA-3948
> URL: https://issues.apache.org/jira/browse/TIKA-3948
> Project: Tika
> Issue Type: Task
>Reporter: Tim Allison
>Priority: Major
> Labels: tika-3x
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [tika] dependabot[bot] opened a new pull request, #1304: Bump aws.version from 1.12.536 to 1.12.537
dependabot[bot] opened a new pull request, #1304: URL: https://github.com/apache/tika/pull/1304 Bumps `aws.version` from 1.12.536 to 1.12.537. Updates `com.amazonaws:aws-java-sdk-s3` from 1.12.536 to 1.12.537 Changelog Sourced from https://github.com/aws/aws-sdk-java/blob/master/CHANGELOG.md";>com.amazonaws:aws-java-sdk-s3's changelog. 1.12.537 2023-08-24 AWS Elemental MediaConvert Features This release includes additional audio channel tags in Quicktime outputs, support for film grain synthesis for AV1 outputs, ability to create audio-only FLAC outputs, and ability to specify Amazon S3 destination storage class. AWS Elemental MediaLive Features MediaLive now supports passthrough of KLV data to a HLS output group with a TS container. MediaLive now supports setting an attenuation mode for AC3 audio when the coding mode is 3/2 LFE. MediaLive now supports specifying whether to include filler NAL units in RTMP output group settings. AWS Glue Features Added API attributes that help in the monitoring of sessions. AWS MediaTailor Features Adds new source location AUTODETECT_SIGV4 access type. AWS S3 Control Features Updates to endpoint ruleset tests to address Smithy validation issues and standardize the capitalization of DualStack. Amazon Elastic Compute Cloud Features Amazon EC2 M7a instances, powered by 4th generation AMD EPYC processors, deliver up to 50% higher performance compared to M6a instances. Amazon EC2 Hpc7a instances, powered by 4th Gen AMD EPYC processors, deliver up to 2.5x better performance compared to Amazon EC2 Hpc6a instances. Amazon QuickSight Features Excel support in Snapshot Export APIs. Removed Required trait for some insight Computations. Namespace-shared Folders support. Global Filters support. Table pin Column support. Amazon Relational Database Service Features This release updates the supported versions for Percona XtraBackup in Aurora MySQL. Amazon Simple Storage Service Features Updates to endpoint ruleset tests to address Smithy validation issues. Amazon Verified Permissions Features Documentation updates for Amazon Verified Permissions. Commits https://github.com/aws/aws-sdk-java/commit/6e9f92b9aef907abd82a67e730ad5da999a337fc";>6e9f92b AWS SDK for Java 1.12.537 https://github.com/aws/aws-sdk-java/commit/52997b66f9ac53d580d52bacf6f90a8fb1d1b93a";>52997b6 Update GitHub version number to 1.12.537-SNAPSHOT See full diff in https://github.com/aws/aws-sdk-java/compare/1.12.536...1.12.537";>compare view Updates `com.amazonaws:aws-java-sdk-transcribe` from 1.12.536 to 1.12.537 Changelog Sourced from https://github.com/aws/aws-sdk-java/blob/master/CHANGELOG.md";>com.amazonaws:aws-java-sdk-transcribe's changelog. 1.12.537 2023-08-24 AWS Elemental MediaConvert Features This release includes additional audio channel tags in Quicktime outputs, support for film grain synthesis for AV1 outputs, ability to create audio-only FLAC outputs, and ability to specify Amazon S3 destination storage class. AWS Elemental MediaLive Features MediaLive now supports passthrough of KLV data to a HLS output group with a TS container. MediaLive now supports setting an attenuation mode for AC3 audio when the coding mode is 3/2 LFE. MediaLive now supports specifying whether to include filler NAL units in RTMP output group settings. AWS Glue Features Added API attributes that help in the monitoring of sessions. AWS MediaTailor Features Adds new source location AUTODETECT_SIGV4 access type. AWS S3 Control Features Updates to endpoint ruleset tests to address Smithy validation issues and standardize the capitalization of DualStack. Amazon Elastic Compute Cloud Features Amazon EC2 M7a instances, powered by 4th generation AMD EPYC processors, deliver up to 50% higher performance compared to M6a instances. Amazon EC2 Hpc7a instances, powered by 4th Gen AMD EPYC processors, deliver up to 2.5x better performance compared to Amazon EC2 Hpc6a instances. Amazon QuickSight Features Excel support in Snapshot Export APIs. Removed Required trait for some insight Computations. Namespace-shared Folders support. Global Filters support. Table pin Column support. Amazon Relational Database Service Features This release updates the supported versions for Percona XtraBackup in Aurora MySQL. Amazon Simple Storage Service
[GitHub] [tika] THausherr merged pull request #1304: Bump aws.version from 1.12.536 to 1.12.537
THausherr merged PR #1304: URL: https://github.com/apache/tika/pull/1304 -- 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
