manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Karl Wright <daddy...@gmail.com>
Subject Re: Chalitha's OpenNLP Transformation Connector Contribution
Date Fri, 18 Dec 2015 12:00:45 GMT
If the models are immutable resources, then we should probably just bundle
them in the jar as resources.  If they are modifiable and/or it is expected
that the user will supply their own, then configuration information is the
way to go.

Karl


On Fri, Dec 18, 2015 at 6:58 AM, Karl Wright <daddywri@gmail.com> wrote:

> Hi Rafa,
>
> I'm also not really happy with how the connector locates the models.  It's
> not going to work very well in a distributed environment.  It seems like
> there's a missing piece here: the models should probably be imported as
> part of the connection's configuration information, rather than just an
> implicit file reference.  How big are these model files, typically?
>
> Karl
>
>
> On Fri, Dec 18, 2015 at 6:53 AM, Karl Wright <daddywri@gmail.com> wrote:
>
>> Yes, please create a ticket.  But I'd create a branch and import the code
>> into that first.  I have to get licenses and build process working before
>> we can bring everything into trunk.
>>
>> Thanks,
>> Karl
>>
>>
>> On Fri, Dec 18, 2015 at 6:38 AM, Rafa Haro <rharo@apache.org> wrote:
>>
>>> Hi all,
>>>
>>> I was about to open a Jira ticket for including Chalitha's OpenNLP
>>> Transformation Connector (
>>> https://github.com/ChalithaUdara/OpenNLP-Manifold-Connector) into the
>>> trunk.
>>>
>>> Everyone agree?
>>>
>>> Cheers,
>>> Rafa
>>>
>>
>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message