[
https://issues.apache.org/jira/browse/TIKA-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lewis John McGibbney resolved TIKA-3360.
Resolution: Fixed
Release successfully made to Artifactory. The entire process is
[
https://issues.apache.org/jira/browse/TIKA-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lewis John McGibbney updated TIKA-3360:
---
Fix Version/s: 1.26
> Retrospective release of tika-helm for tika-docker 1.26 and
We have to clean up packaging. I’m intentionally not bundling all of the
fetchers and emitters with the Tika-server jar. We should have the main
class add those at runtime or (worse) require users to add them to their
class path
On Wed, Apr 21, 2021 at 1:17 PM Giovanni De Stefano
wrote:
> Hello
[
https://issues.apache.org/jira/browse/TIKA-3362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Giovanni De Stefano closed TIKA-3362.
-
> AsyncParser and EmitterResource have handler type hardcoded to text
>
[
https://issues.apache.org/jira/browse/TIKA-3362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17326470#comment-17326470
]
Giovanni De Stefano commented on TIKA-3362:
---
Thanks! It works :)
> AsyncParser and
(sorry all, ignore this. was intended to be sent to users list)
On Wed, Apr 21, 2021 at 10:45 AM Nicholas DiPiazza <
nicholas.dipia...@gmail.com> wrote:
> Hi Tika Users:
>
> Does Tika have any built-in Title extract logic?
>
> I am currently using a simple algorithm that:
>
> 1) Checks metadata
lewismc opened a new pull request #1:
URL: https://github.com/apache/tika-helm/pull/1
This ticket will act as the basis of the 1.26-full tika-helm release.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
lewismc merged pull request #1:
URL: https://github.com/apache/tika-helm/pull/1
--
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.
For queries about this service, please
[
https://issues.apache.org/jira/browse/TIKA-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lewis John McGibbney updated TIKA-3360:
---
Summary: Retrospective release of tika-helm for tika-docker 1.26 and
1.26-full (was:
[
https://issues.apache.org/jira/browse/TIKA-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17326681#comment-17326681
]
Lewis John McGibbney commented on TIKA-3360:
OK so it turns out that Apache INFRA has deployed
Hi Tika Users:
Does Tika have any built-in Title extract logic?
I am currently using a simple algorithm that:
1) Checks metadata for a title. Use that if there.
2) If no title metadata, then use the body text. Extract the first line of
the body text and use that as the title.
So let's say we
Hello all, @TimAllison
I am using tika-server-classic.
I post to AsyncResource: let’s say 100 AsyncRequest with each 1 FetchEmitTuple.
I receive 100 ok added responses.
AsyncEmitter starts polling each of those 100 FetchEmitTuple and begins
processing: when AsyncParser fails, the server
After your last request, this is the next on my list... how did you get
ahold of my list?!
There’s an alpha async parser that persists requests and emit data in an h2
db. I have to wire that into the async handler in Tika-server.
I’d normally welcome the help but this is all so new, lemme take a
[
https://issues.apache.org/jira/browse/TIKA-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17326748#comment-17326748
]
Lewis John McGibbney commented on TIKA-3360:
I'm documenting all of my activity at
[
https://issues.apache.org/jira/browse/TIKA-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17326773#comment-17326773
]
Lewis John McGibbney commented on TIKA-3360:
Final part, releasing to Artifactory is being
[
https://issues.apache.org/jira/browse/TIKA-3357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17327090#comment-17327090
]
ASF GitHub Bot commented on TIKA-3357:
--
Subhajitdas298 opened a new pull request #430:
URL:
Subhajitdas298 opened a new pull request #430:
URL: https://github.com/apache/tika/pull/430
Added Resource comparator based to produce type.
In an ambiguous call, request handler will be chosen based on the type of
data it returns.
*Current priority is set as:*
[
https://issues.apache.org/jira/browse/TIKA-3327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Subhajit Das updated TIKA-3327:
---
Affects Version/s: 2.0.0
> Simple server metrics monitoring
>
>
>
[
https://issues.apache.org/jira/browse/TIKA-3327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Subhajit Das reopened TIKA-3327:
Reopened for 2.x lineup
> Simple server metrics monitoring
>
>
>
[
https://issues.apache.org/jira/browse/TIKA-3357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Subhajit Das updated TIKA-3357:
---
Affects Version/s: 2.0.0
> Remove ambiguity in request handlers
>
[
https://issues.apache.org/jira/browse/TIKA-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17327069#comment-17327069
]
ASF GitHub Bot commented on TIKA-3353:
--
Subhajitdas298 commented on pull request #429:
URL:
[
https://issues.apache.org/jira/browse/TIKA-3327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Subhajit Das updated TIKA-3327:
---
Summary: Simple server metrics monitoring (server status over JMX) (was:
Simple server metrics
Subhajitdas298 commented on pull request #429:
URL: https://github.com/apache/tika/pull/429#issuecomment-824499807
@tballison Please review the PR and let me know, if anything has to be
modified.
--
This is an automated message from the Apache Git Service.
To respond to the message,
23 matches
Mail list logo
