[jira] [Closed] (UIMA-5634) DUCC Orchestrator (OR) populate DB with Job and Managed Reservation specifications

[Lou DeGenaro (JIRA)]

 [ 
https://issues.apache.org/jira/browse/UIMA-5634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lou DeGenaro closed UIMA-5634.
--

> DUCC Orchestrator (OR) populate DB with Job and Managed Reservation 
> specifications
> --
>
> Key: UIMA-5634
> URL: https://issues.apache.org/jira/browse/UIMA-5634
> Project: UIMA
>  Issue Type: Improvement
>  Components: DUCC
>Reporter: Lou DeGenaro
>Assignee: Lou DeGenaro
>Priority: Major
> Fix For: 2.2.2-Ducc
>
>
> Presently, Job and Managed Reservation specifications are kept in "user" 
> space, that is in the file system in the user's log directory.  
> The Command Line Interface (CLI) should no longer write these specifications 
> to the file system, but rather when submitted to the Orchestrator (OR) they 
> should be persisted in the DB for later retrieval.  This accomplishes 2 
> desirable outcomes: 
> 1. The specification persists after the user purges his/her log directory
> 2. The specification is available to the Web Server (ducc-mon) when there is 
> no shared file system



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (UIMA-5634) DUCC Orchestrator (OR) populate DB with Job and Managed Reservation specifications

[Lou DeGenaro (JIRA)]

 [ 
https://issues.apache.org/jira/browse/UIMA-5634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lou DeGenaro resolved UIMA-5634.

Resolution: Fixed

Change set delivered.

> DUCC Orchestrator (OR) populate DB with Job and Managed Reservation 
> specifications
> --
>
> Key: UIMA-5634
> URL: https://issues.apache.org/jira/browse/UIMA-5634
> Project: UIMA
>  Issue Type: Improvement
>  Components: DUCC
>Reporter: Lou DeGenaro
>Assignee: Lou DeGenaro
>Priority: Major
> Fix For: 2.2.2-Ducc
>
>
> Presently, Job and Managed Reservation specifications are kept in "user" 
> space, that is in the file system in the user's log directory.  
> The Command Line Interface (CLI) should no longer write these specifications 
> to the file system, but rather when submitted to the Orchestrator (OR) they 
> should be persisted in the DB for later retrieval.  This accomplishes 2 
> desirable outcomes: 
> 1. The specification persists after the user purges his/her log directory
> 2. The specification is available to the Web Server (ducc-mon) when there is 
> no shared file system



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [ANNOUNCE] Apache UIMA AS 2.10.2 released

[Jaroslaw Cwiklik]

Thanks for your comments. Perhaps I was a little skimpy in the description.
The announcement does
include a link to more information about the project. I figured that if
some was interested he/she would
explore the linked content. I do agree that more info is needed to get
someone to ask for more :)

Will do better next time!

Regards, Jerry
UIMA Team

On Fri, Feb 9, 2018 at 12:02 PM, sebb  wrote:

> On 9 February 2018 at 14:14, Jerry Cwiklik  wrote:
> > The Apache UIMA team is pleased to announce the release of the Apache
> > UIMA-AS version 2.10.2, which includes asynchronous scaleout capabilities
> > for the UIMA annotators.
>
> What is the project about? Why should I be interested in it?
> [rhetorical questions]
>
> The Announce emails are sent to people not on the developer or user lists.
> Most will have no idea what the project is about.
>
> So the e-mails should contain at least brief details of what the
> product does, and some info on why the new release might be of
> interest to them.
>
> Readers should not have to click links to find out the basic information
> (although of course it is useful to have such links for further detail).
>
> Please can you add that information to future announce mails?
>
> Also it would be helpful to include the download link.
>
> Thanks.
>
>
> > UIMA-AS includes the base UIMA SDK and augments it with scaleout
> capability;
> > it is a next-generation replacement for the original CPM (Collection
> > Processing Management) scaleout that is part of the core UIMA Framework.
> For
> > more information, please visit:
> >
> > http://uima.apache.org/doc-uimaas-what.html
> >
> > This release contains a number of improvements and bug fixes. Notable
> > updates in this release include:
> > - Updated to use ActiveMQ 5.15.2 (requires Java 1.8)
> > - Added dependency on UIMA SDK 2.10.2
> > - Fixed merging of type priorities
> > - Added support for targeting specific service instance
> > - Fixed per CAS Performance Metrics breakdown
> > - Fixed eclipse examples import
> > - Fixed dd2spring issues
> > - Fixed JMS listener recovery after service restart
> >
> > For a complete list of bugs and improvements included in this release
> please
> > see
> > https://uima.apache.org/d/uima-as-2.10.2/issuesFixed/jira-report.html.
> >
> > -- Jerry Cwiklik, for the Apache UIMA development team
> >
>

Re: [ANNOUNCE] Apache UIMA AS 2.10.2 released

[sebb]

On 9 February 2018 at 14:14, Jerry Cwiklik  wrote:
> The Apache UIMA team is pleased to announce the release of the Apache
> UIMA-AS version 2.10.2, which includes asynchronous scaleout capabilities
> for the UIMA annotators.

What is the project about? Why should I be interested in it?
[rhetorical questions]

The Announce emails are sent to people not on the developer or user lists.
Most will have no idea what the project is about.

So the e-mails should contain at least brief details of what the
product does, and some info on why the new release might be of
interest to them.

Readers should not have to click links to find out the basic information
(although of course it is useful to have such links for further detail).

Please can you add that information to future announce mails?

Also it would be helpful to include the download link.

Thanks.


> UIMA-AS includes the base UIMA SDK and augments it with scaleout capability;
> it is a next-generation replacement for the original CPM (Collection
> Processing Management) scaleout that is part of the core UIMA Framework. For
> more information, please visit:
>
> http://uima.apache.org/doc-uimaas-what.html
>
> This release contains a number of improvements and bug fixes. Notable
> updates in this release include:
> - Updated to use ActiveMQ 5.15.2 (requires Java 1.8)
> - Added dependency on UIMA SDK 2.10.2
> - Fixed merging of type priorities
> - Added support for targeting specific service instance
> - Fixed per CAS Performance Metrics breakdown
> - Fixed eclipse examples import
> - Fixed dd2spring issues
> - Fixed JMS listener recovery after service restart
>
> For a complete list of bugs and improvements included in this release please
> see
> https://uima.apache.org/d/uima-as-2.10.2/issuesFixed/jira-report.html.
>
> -- Jerry Cwiklik, for the Apache UIMA development team
>

[jira] [Resolved] (UIMA-5551) Add registry support so pull services can locate their server

[Burn Lewis (JIRA)]

 [ 
https://issues.apache.org/jira/browse/UIMA-5551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Burn Lewis resolved UIMA-5551.
--
Resolution: Fixed

Replaced the -D specifying the pull service config file by an explicit -D 
specifying the registry and the name to look up.  Moved the registration of a 
service driver out of DuccServiceDriver for more flexibility. Dropped the 
ConfigurationProperties class.

> Add registry support so pull services can locate their server
> -
>
> Key: UIMA-5551
> URL: https://issues.apache.org/jira/browse/UIMA-5551
> Project: UIMA
>  Issue Type: New Feature
>  Components: DUCC
>Reporter: Burn Lewis
>Assignee: Burn Lewis
>Priority: Major
> Fix For: 2.2.2-Ducc
>
>
> Optionally allow pull services to use a registry to locate resources such as 
> their server and other services such as a database.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (UIMA-5724) UIMA-AS: eclipse update site build not working correctly

[Jerry Cwiklik (JIRA)]

Jerry Cwiklik created UIMA-5724:
---

 Summary: UIMA-AS: eclipse update site build not working correctly
 Key: UIMA-5724
 URL: https://issues.apache.org/jira/browse/UIMA-5724
 Project: UIMA
  Issue Type: Bug
  Components: Async Scaleout
Reporter: Jerry Cwiklik
Assignee: Jerry Cwiklik
 Fix For: 2.10.3AS


The UIMA-AS eclipse update site build is not copying 2 artifacts to the plugins 
folder:

org.apache.uima.runtime.fragments.deployeditor_2.10.2.jar.pack.gz 

org.apache.uima.deployeditor_2.10.2.jar.pack.gz

 

These artifacts are created by the build in eus-work folder but never copied to 
the plugins folder. Only the signature files for the above are copied.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (UIMA-5723) MARKTABLE fails to assign feature for single word entry in first CSV column

[Andreas Thiel (JIRA)]

Andreas Thiel created UIMA-5723:
---

 Summary: MARKTABLE fails to assign feature for single word entry 
in first CSV column
 Key: UIMA-5723
 URL: https://issues.apache.org/jira/browse/UIMA-5723
 Project: UIMA
  Issue Type: Bug
  Components: Ruta
Affects Versions: 2.6.1ruta
Reporter: Andreas Thiel


When using Ruta's MARKTABLE action with a CSV file {{nl_law_names.csv}} like 
this
{code:xml}
WAZ;WAZELF
Wet arbeidsongeschiktheidsverzekering zelfstandigen;WAZELF
{code}
and corresponding Ruta script containing these lines
{code:java}
WORDTABLE LawNameTable = 'nl_law_names.csv';
Document{->MARKTABLE(WetNaam, 1, LawNameTable, "WetIdentifier" = 2)};
{code}
it seems that the text {{WAZ}} is detected, but the {{WetIdentifier}} feature 
of the resulting annotation is not filled by the string following the 
semicolon. Instead, it remains empty.

(Note: _WetNaam_ annotation is defined elsewhere via type system description)

In contrast, the fully written name {{Wet arbeidsongeschiktheidsverzekering 
zelfstandigen}} is detected and processed as expected with feature 
WetIdentifier = WAZELF after annnotating.

Could it be that problems arise when only a single word (i.e. no spaces or 
uppercase letters following lowercase chars) is present in the first column in 
the CSV file? Or is it a matter of configuration?

We experimented also with the optional arguments of MARKTABLE regarding 
uppercase/lowercase distinction, but to no avail.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)