On Mon, 15 Jun 2015, Mattmann, Chris A (3980) wrote:
Hey nick I guess my point is that parser context aka config properties
for parsers and custom config files e.g., x.properties loaded from the
classpath aren't configured from Tika app or server
Ah, good point. In my ideal world, you'd set th
Tim Allison created TIKA-1657:
-
Summary: Allow easier dumping of TikaConfig file from tika-core
Key: TIKA-1657
URL: https://issues.apache.org/jira/browse/TIKA-1657
Project: Tika
Issue Type: Impro
[
https://issues.apache.org/jira/browse/TIKA-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14586235#comment-14586235
]
Tim Allison edited comment on TIKA-1508 at 6/15/15 4:10 PM:
To
[
https://issues.apache.org/jira/browse/TIKA-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14586245#comment-14586245
]
Tim Allison commented on TIKA-1508:
---
>From [~gagravarr],
{quote}
> My personal view is th
Yeah we should read props from Tika config and flow into parse context
Sent from my iPhone
> On Jun 15, 2015, at 8:57 AM, Tim Allison (JIRA) wrote:
>
>
>[
> https://issues.apache.org/jira/browse/TIKA-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommen
[
https://issues.apache.org/jira/browse/TIKA-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14586235#comment-14586235
]
Tim Allison commented on TIKA-1508:
---
To respond to Nick's point about including concrete
[
https://issues.apache.org/jira/browse/TIKA-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14586227#comment-14586227
]
Tim Allison commented on TIKA-1508:
---
>From the dev list, it looks like there is interest
Hey nick I guess my point is that parser context aka config properties for
parsers and custom config files e.g., x.properties loaded from the classpath
aren't configured from Tika app or server
Sent from my iPhone
> On Jun 15, 2015, at 8:34 AM, Nick Burch wrote:
>
>> On Mon, 15 Jun 2015, Mat
On Mon, 15 Jun 2015, Mattmann, Chris A (3980) wrote:
We also need to be mindful of Tika app and sever where there is no
current way to see config other than Tika config file and multiple
conflicting ways to set it...
Hmm? Both app and server optionally take a config file, don't they? And
both
I think, there's a third concern should be taken in account: dynamic
configuration (e.g. based on metadata, like password provider on
per-document basis).
Currently you only can inject some dynamically configurable behavior via
ParseContext, but it adds complexity to recursive parser implementation
We also need to be mindful of Tika app and sever where there is no current way
to see config other than Tika config file and multiple conflicting ways to set
it...
Sent from my iPhone
> On Jun 15, 2015, at 8:02 AM, Nick Burch wrote:
>
>> On Mon, 15 Jun 2015, Allison, Timothy B. wrote:
>> Agre
On Mon, 15 Jun 2015, Allison, Timothy B. wrote:
Agreed. They are two separate but related issues. TIKA-1508 should be
fairly straightforward. Should I start coding it? Any other
recommendations/concerns?
My personal view is that properties/configuration which apply to all
documents of a t
Agreed. They are two separate but related issues. TIKA-1508 should be fairly
straightforward. Should I start coding it? Any other recommendations/concerns?
-Original Message-
From: Tyler Palsulich [mailto:tpalsul...@gmail.com]
Sent: Saturday, June 13, 2015 12:54 PM
To: dev@tika.apa
13 matches
Mail list logo
