[
https://issues.apache.org/jira/browse/TIKA-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14385803#comment-14385803
]
Uwe Schindler commented on TIKA-1511:
-------------------------------------
Solr uses ANT + IVY to build. We don't use transitive dependencies at all! So
whenever updating TIKA, the person who does this prints the dependency tree and
then fills all required information into the ivy.xml file and our
ivy-versions.properties file :-) In general, we carefully decide, which
dependencies are really needed. Because TIKA automatically disables parser
which do not load, we have already removed various files (like netcdf parser -
> LGPL) or the ASM parser (we dont support "indexing" Java Class files by
default).
For the current one: We dont want to have native libraries anywhere (we don't
even ship our own native libs for WindowsDirectory). Users need to do this
themselves start msvcc/gcc. So we would not ship wth SQLite support by default.
In general it would be good to have some easier plugin mechanism to allow Solr
to pick only some parsers they ship by default and those the user can download
(e.g. by a script). So it would be good to have multiple parser-JARS. So maybe
put all "crazy" parsers that fork processes or call native libs into a separate
TIKA parser bundle. The default one should only have pure-java stuff with as
few dependencies as possible...
> Create a parser for SQLite3
> ---------------------------
>
> Key: TIKA-1511
> URL: https://issues.apache.org/jira/browse/TIKA-1511
> Project: Tika
> Issue Type: New Feature
> Components: parser
> Affects Versions: 1.6
> Reporter: Luis Filipe Nassif
> Fix For: 1.8
>
> Attachments: TIKA-1511v1.patch, TIKA-1511v2.patch, TIKA-1511v3.patch,
> TIKA-1511v3bis.patch, testSQLLite3b.db, testSQLLite3b.db
>
>
> I think it would be very useful, as sqlite is used as data storage by a wide
> range of applications. Opening the ticket to track it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
