[JBoss JIRA] (TEIID-3693) Add data source support for reading documents (i.e., RTF, DOC, PDF)
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3693?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3693:
---------------------------------------
Also we need to identify when there are opportunities to leverage other jboss functionality such as existing modeshape sequencing, esb, or document transformation capabilities that may be more targeted at a document workflow, which could directly produce the desired output in xml/json/csv.
> Add data source support for reading documents (i.e., RTF, DOC, PDF)
> -------------------------------------------------------------------
>
> Key: TEIID-3693
> URL: https://issues.jboss.org/browse/TEIID-3693
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Reporter: Van Halbert
> Assignee: Van Halbert
>
> Add data source support for reading documents (i.e., RTF, DOC, PDF).
> From a runtime perspective the extraction logic is straight-forward when there is a parsing library. Here's one from CA using JSoup - https://github.com/rokhmanov/teiid-translators/blob/master/translator-scr...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (TEIID-2729) Dynamic VDB xml requires sibling elements to be in a certain order
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2729?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2729:
----------------------------------
Fix Version/s: (was: 8.7)
> Dynamic VDB xml requires sibling elements to be in a certain order
> ------------------------------------------------------------------
>
> Key: TEIID-2729
> URL: https://issues.jboss.org/browse/TEIID-2729
> Project: Teiid
> Issue Type: Enhancement
> Components: AdminApi
> Affects Versions: 8.5
> Reporter: Mark Drilling
> Assignee: Steven Hawkins
>
> In my *-vdb.xml, I have a model defined per following snippet:
> <model name="myModel" type="PHYSICAL" visible="true">
> <source name="myModel" translator-name="hive" connection-jndi-name="Hive12Src" />
> <property name="trimColumnNames" value="true" />
> </model>
> The vdb.xml failed to parse, so I moved the <property> element ahead of <source> and then it worked.
> I don't think element ordering should matter in this case?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (TEIID-3693) Add data source support for reading documents (i.e., RTF, DOC, PDF)
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3693?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3693:
---------------------------------------
Make sure to also indicate per doc type what the extraction expectations are - tabular/scalar value, what the extraction language should be - is there a standard path syntax, or something that we need to come up with, and the necessary designer integration as well.
> Add data source support for reading documents (i.e., RTF, DOC, PDF)
> -------------------------------------------------------------------
>
> Key: TEIID-3693
> URL: https://issues.jboss.org/browse/TEIID-3693
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Reporter: Van Halbert
> Assignee: Van Halbert
>
> Add data source support for reading documents (i.e., RTF, DOC, PDF).
> From a runtime perspective the extraction logic is straight-forward when there is a parsing library. Here's one from CA using JSoup - https://github.com/rokhmanov/teiid-translators/blob/master/translator-scr...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months