[jira] Closed: (UIMA-1349) Documentation does not mention that resource implementation should implement
[ https://issues.apache.org/jira/browse/UIMA-1349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor closed UIMA-1349. Resolution: Fixed Fix Version/s: 2.3 Documentation does not mention that resource implementation should implement - Key: UIMA-1349 URL: https://issues.apache.org/jira/browse/UIMA-1349 Project: UIMA Issue Type: Bug Components: Documentation Affects Versions: 2.2.2 Reporter: Pablo Duboue Priority: Minor Fix For: 2.3 In page 37 of the 2.2.2 documentation (section 1.5.4.3) it should say that StringMapResource_impl should implement org.apache.uima.resource.SharedResourceObject. (That's where the 'load' method comes from.) This is trivial to fix but it really hampers the understanding of the section. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1320) Parameter Definitions dialog does not allow parameters with same name in different groups.
[ https://issues.apache.org/jira/browse/UIMA-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor updated UIMA-1320: - Affects Version/s: 2.3 defer past 2.3.0 Parameter Definitions dialog does not allow parameters with same name in different groups. -- Key: UIMA-1320 URL: https://issues.apache.org/jira/browse/UIMA-1320 Project: UIMA Issue Type: Bug Components: Eclipse plugins Affects Versions: 2.2.2, 2.3 Reporter: Kai Schlamp Priority: Minor The Parameter Definitions dialog of the Component Descriptor Editor does not allow me to add identifiers with the same name in different groups (Error: Parameter Names must be unique), although the Tutorial and Users Guide says in 1.2.1.4 that this is possible. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1302) PerformanceReports for PEAR not being generated in a CPE
[ https://issues.apache.org/jira/browse/UIMA-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor closed UIMA-1302. Resolution: Fixed Fix Version/s: 2.3 Should be fixed by fixes in linked issue. If not, please re-open PerformanceReports for PEAR not being generated in a CPE - Key: UIMA-1302 URL: https://issues.apache.org/jira/browse/UIMA-1302 Project: UIMA Issue Type: Bug Components: Collection Processing Affects Versions: 2.2.2 Reporter: Kevin Cunnane Priority: Minor Fix For: 2.3 When an installed PEAR is included as an AE in a Collection Processing Engine, the performance report generated by the CPE doesn't include any figures for the PEAR. The only work-around is to install the pear and then reference the AE descriptor directly, however this ruins the entire point of using the PEAR - it automatically sets the classpath, datapath etc for you. I discussed this issue with Thilo Goetz, who said I should raise a bug against it. Please see correspondence below about this issue with Thilo. *My Message:* Hi Thilo, I work for the LanguageWare team in Dublin, and am having an issue getting performance numbers for PEARs used in a Collection Processing Engine. Essentially, when you refer to the PEAR using the pearSpecifier file, then the performance of the PEAR is not included in the Performance Report. However, if you run the PEAR by referring to its main descriptor directly (and setting up the classpath etc manually) you will correctly get the performance of the components in the PEAR included in the performance report. Am I doing something wrong, or is there a way to work around this? For example, is this just an issue when using PEARs in a CPE, or can I get the information some other way? I'm trying to set up an automated process for testing the performance of a PEAR against a corpus, and would like to avoid having to write code / scripts for this *His Responses:* Hi Kevin, that issue somehow seems familiar. I've looked into those PerformanceReports because of another bug I found, and I think I noticed this, too (http://www.mail-archive.com/uima-dev%40incubator.apache.org/msg06565.html). So I think this is a UIMA issue, due to the special nature of pear descriptors (they are not regular AE descriptors). So the only workaround I can think of at this time is to not use pears, or install the pear and then reference the AE descriptor directly, if that's possible. *Related Posts* I found this post http://markmail.org/message/doknwh5iecuhtai3 that seems to refer to the exact same issue -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1291) FileNotFoundException with addSourceToJars under Windows when UIMA_HOME contains whitespace
[ https://issues.apache.org/jira/browse/UIMA-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor closed UIMA-1291. Resolution: Fixed FileNotFoundException with addSourceToJars under Windows when UIMA_HOME contains whitespace --- Key: UIMA-1291 URL: https://issues.apache.org/jira/browse/UIMA-1291 Project: UIMA Issue Type: Bug Components: Tools Affects Versions: 2.2.2 Environment: Windowx XP Reporter: Kai Schlamp Priority: Trivial When executing addSourceToJars MS-DOS batch file under Windows and the UIMA_HOME variable has whitespace in it (like C:\Program Files\apache-uima), then one gets errors of the following type: C:\..\uimaj-2.2.2-incubating\jVinci\src\main\javajar -uvf C:\Program Files\apache-uima\lib\jVinci.jar * java.io.FileNotFoundException: C:\Program (The system cannot find the file specified) A solution is to simply surround the %UIMA_HOME% strings in addSourceToJars with quotations, for example: jar -uvf %UIMA_HOME%\lib\jVinci.jar * -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1291) FileNotFoundException with addSourceToJars under Windows when UIMA_HOME contains whitespace
[ https://issues.apache.org/jira/browse/UIMA-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor updated UIMA-1291: - Fix Version/s: 2.3 FileNotFoundException with addSourceToJars under Windows when UIMA_HOME contains whitespace --- Key: UIMA-1291 URL: https://issues.apache.org/jira/browse/UIMA-1291 Project: UIMA Issue Type: Bug Components: Tools Affects Versions: 2.2.2 Environment: Windowx XP Reporter: Kai Schlamp Priority: Trivial Fix For: 2.3 When executing addSourceToJars MS-DOS batch file under Windows and the UIMA_HOME variable has whitespace in it (like C:\Program Files\apache-uima), then one gets errors of the following type: C:\..\uimaj-2.2.2-incubating\jVinci\src\main\javajar -uvf C:\Program Files\apache-uima\lib\jVinci.jar * java.io.FileNotFoundException: C:\Program (The system cannot find the file specified) A solution is to simply surround the %UIMA_HOME% strings in addSourceToJars with quotations, for example: jar -uvf %UIMA_HOME%\lib\jVinci.jar * -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1289) If an aggregate uses the unsupported include instead of import a very very very obscure error message results
[ https://issues.apache.org/jira/browse/UIMA-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor updated UIMA-1289: - Affects Version/s: 2.3 defer past 2.3.0 If an aggregate uses the unsupported include instead of import a very very very obscure error message results - Key: UIMA-1289 URL: https://issues.apache.org/jira/browse/UIMA-1289 Project: UIMA Issue Type: Bug Components: Core Java Framework Affects Versions: 2.2.2, 2.3 Reporter: Burn Lewis Priority: Minor In converting a CPE descriptor to an aggregate descriptor I forgot to change one include ... to import The docs indicate that include is not supported but the CDE error message was: ResourceInitializationException: The CasCreationUtils.createCas method was passed a collection containing an object of class org.apache.uima.collection.impl.metadata.cpe.CpeIncludeImpl, which is not supported. Not very helpful! The cvd reported a stack trace but still no clue as to what part of what file was in error: org.apache.uima.tools.cvd.MainFrame.handleException(575): SEVERE: org.apache.uima.collection.impl.metadata.cpe.CpeIncludeImpl incompatible with org.apache.uima.resource.ResourceSpecifier java.lang.ClassCastException: org.apache.uima.collection.impl.metadata.cpe.CpeIncludeImpl incompatible with org.apache.uima.resource.ResourceSpecifier at org.apache.uima.analysis_engine.impl.AnalysisEngineDescription_impl.getComponentSpecifier(AnalysisEngineDescription_impl.java:439) at org.apache.uima.analysis_engine.impl.AnalysisEngineDescription_impl.checkForInvalidParameterOverrides(AnalysisEngineDescription_impl.java:380) at org.apache.uima.resource.impl.ResourceCreationSpecifier_impl.validateConfigurationParameters(ResourceCreationSpecifier_impl.java:246) at org.apache.uima.resource.impl.ResourceCreationSpecifier_impl.validate(ResourceCreationSpecifier_impl.java:219) at org.apache.uima.analysis_engine.impl.AnalysisEngineDescription_impl.validate(AnalysisEngineDescription_impl.java:304) at org.apache.uima.analysis_engine.impl.AggregateAnalysisEngine_impl.initialize(AggregateAnalysisEngine_impl.java:163) at org.apache.uima.impl.AnalysisEngineFactory_impl.produceResource(AnalysisEngineFactory_impl.java:94) at org.apache.uima.impl.CompositeResourceFactory_impl.produceResource(CompositeResourceFactory_impl.java:62) at org.apache.uima.UIMAFramework.produceResource(UIMAFramework.java:258) at org.apache.uima.UIMAFramework.produceResource(UIMAFramework.java:303) at org.apache.uima.UIMAFramework.produceAnalysisEngine(UIMAFramework.java:383) at org.apache.uima.tools.cvd.MainFrame.setupAE(MainFrame.java:1529) at org.apache.uima.tools.cvd.MainFrame.loadAEDescriptor(MainFrame.java:524) at org.apache.uima.tools.cvd.control.AnnotatorOpenEventHandler.actionPerformed(AnnotatorOpenEventHandler.java:52) at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:2006) at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2329) at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:398) at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:253) at javax.swing.AbstractButton.doClick(AbstractButton.java:368) at javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1231) at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:1272) at java.awt.Component.processMouseEvent(Component.java:6052) at javax.swing.JComponent.processMouseEvent(JComponent.java:3276) at java.awt.Component.processEvent(Component.java:5817) at java.awt.Container.processEvent(Container.java:2069) at java.awt.Component.dispatchEventImpl(Component.java:4424) at java.awt.Container.dispatchEventImpl(Container.java:2127) at java.awt.Component.dispatchEvent(Component.java:4254) at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4333) at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3997) at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3927) at java.awt.Container.dispatchEventImpl(Container.java:2113) at java.awt.Window.dispatchEventImpl(Window.java:2451) at java.awt.Component.dispatchEvent(Component.java:4254) at java.awt.EventQueue.dispatchEvent(EventQueue.java:610) at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:284) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:194) at
[jira] Updated: (UIMA-17) Do missing documentation parts
[ https://issues.apache.org/jira/browse/UIMA-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor updated UIMA-17: --- Affects Version/s: 2.3 defer past 2.3.0 Do missing documentation parts -- Key: UIMA-17 URL: https://issues.apache.org/jira/browse/UIMA-17 Project: UIMA Issue Type: Task Components: Documentation Affects Versions: 2.3 Reporter: Marshall Schor Priority: Minor Some things in UIMA are not documented, or documented poorly. This task has a list of them. Please edit this Jira issue to add/revise. Perhaps we can have subtasks to identify things we're ready to really work on. 1) UIMA Embedding Framework - how UIMA makes it easy to embed 2) Resource Management (some notes already exist, maybe need integration into main docs?) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1248) ResourceManager initialization is not thread-safe
[ https://issues.apache.org/jira/browse/UIMA-1248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor updated UIMA-1248: - Affects Version/s: 2.3 defer past 2.3.0 ResourceManager initialization is not thread-safe - Key: UIMA-1248 URL: https://issues.apache.org/jira/browse/UIMA-1248 Project: UIMA Issue Type: Bug Components: Core Java Framework Affects Versions: 2.2.2, 2.3 Reporter: Adam Lally Assignee: Adam Lally Priority: Minor If multiple threads concurrently call UIMAFramework.produceAnalysisEngine and pass the same instance of ResourceManager as an argument, you can get intermittent exceptions in the ResourceManager such as: java.lang.ArrayIndexOutOfBoundsException at java.lang.System.arraycopy(Native Method) at java.util.ArrayList.ensureCapacity(ArrayList.java:170) at java.util.ArrayList.add(ArrayList.java:351) at org.apache.uima.resource.impl.CasManager_impl.addMetaData(CasManager_impl.java:82) at org.apache.uima.analysis_engine.impl.AnalysisEngineImplBase.initialize(AnalysisEngineImplBase.java:115) at org.apache.uima.analysis_engine.impl.AggregateAnalysisEngine_impl.initialize(AggregateAnalysisEngine_impl.java:126) The workaround is to synchronize the calls to UIMAFramework.produceAnalysisEngine. However, this is suboptimal if annotator initialization is expensive and you want it to be run in parallel on multiple cores. We should consider adding synchronization to the ResourceManager (and the classes it delegates to such as CasManager) to allow this to work. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (UIMA-1223) Annotators should be initialized in the same thread that their process method will later be called on
[ https://issues.apache.org/jira/browse/UIMA-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor resolved UIMA-1223. -- Resolution: Fixed This is fixed, but in a way that forces serialization. Revisit when linked issue addressed Annotators should be initialized in the same thread that their process method will later be called on - Key: UIMA-1223 URL: https://issues.apache.org/jira/browse/UIMA-1223 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.2.2 Reporter: Adam Lally Assignee: Jerry Cwiklik Priority: Minor Attachments: uimaj-as-activemq-UIMA-1223-patch.txt, uimaj-as-core-UIMA-1223-patch.txt It is more convenient if an annotator is initialized on the same thread that it is later called on. Some components may use thread-local data and they won't work in UIMA-AS currently. Another advantage of doing the initialization in the processing thread is that you could initialize multiple instances of the annotator in parallel instead of sequentially, which may be faster for a multi-core machine. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1204) Pear installer fails on EBCDIC system
[ https://issues.apache.org/jira/browse/UIMA-1204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor updated UIMA-1204: - Affects Version/s: 2.3 defer past 2.3.0 Pear installer fails on EBCDIC system - Key: UIMA-1204 URL: https://issues.apache.org/jira/browse/UIMA-1204 Project: UIMA Issue Type: Bug Components: Tools Affects Versions: 2.2.2, 2.3 Environment: z/OS Reporter: Thilo Goetz Priority: Minor --- Test set: org.apache.uima.tools.pear.merger.PearMergerTest --- Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.973 sec FAILURE! testPearMerger(org.apache.uima.tools.pear.merger.PearMergerTest) Time elapsed: 2.957 sec FAILURE! junit.framework.AssertionFailedError at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at junit.framework.Assert.assertTrue(Assert.java:27) at org.apache.uima.tools.pear.merger.PearMergerTest.testPearMerger(PearMergerTest.java:117) And the following stack trace from stdout: Running org.apache.uima.tools.pear.merger.PearMergerTest [PEAR Merger]: task parameters = Input PEARs = /u/haubenr/uimaj-2.3.0-incubating-SNAPSHOT/uimaj-tools/target/test-classes/pearTests/pearMergerTests/uima.example.DateTime.pear /u/haubenr/uimaj-2.3.0-incubating-SNAPSHOT/uimaj-tools/target/test-classes/pearTests/pearMergerTests/uima.example.RoomNumber.pear Output PEAR = Name = uima.example.RoomDateTimeAggregate File = /tmp/pear_merger_test_23293tmp/uima.example.RoomDateTimeAggregate.pear Output root dir: /u/haubenr/uima.example.RoomDateTimeAggregate [PEAR Merger]: extracting delegate PEARs ... [PEAR Merger]: 141298 bytes extracted successfully [PEAR Merger]: created merged package directory structure [PEAR Merger]: generated aggregate component descriptor [PEAR Merger]: generated aggregate package installation descriptor [PEAR Merger]: created output aggregate PEAR file - /tmp/pear_merger_test_23293tmp/uima.example.RoomDateTimeAggregate.pear [InstallationController]: extracting /tmp/pear_merger_test_23293tmp/uima.example.RoomDateTimeAggregate.pear [InstallationController]: 145657 bytes extracted [InstallationProcessor]: start processing InsD file - /tmp/pear_merger_test_23293tmp/uima.example.RoomDateTimeAggregate/metadata/install.xml Error in InstallationController: java.io.UnsupportedEncodingException: can't detect encoding in /tmp/pear_merger_test_23293tmp/uima.example.RoomDateTimeAggregate/desc/uima.example.RoomDateTimeAggregate.xml java.io.UnsupportedEncodingException: can't detect encoding in /tmp/pear_merger_test_23293tmp/uima.example.RoomDateTimeAggregate/desc/uima.example.RoomDateTimeAggregate.xml at org.apache.uima.pear.util.FileUtil.replaceStringInFile(FileUtil.java:1337) at org.apache.uima.pear.tools.InstallationProcessor.substituteStringVariablesInFiles(InstallationProcessor.java:429) at org.apache.uima.pear.tools.InstallationProcessor.process(InstallationProcessor.java:368) at org.apache.uima.pear.tools.InstallationController.installComponent(InstallationController.java:1569) at org.apache.uima.tools.pear.merger.PearMergerTest.testPearMerger(PearMergerTest.java:116) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140) at
[jira] Updated: (UIMA-1197) cleanup - replace StringBuffer with StringBuilder in those cases where synchronization is not needed
[ https://issues.apache.org/jira/browse/UIMA-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor updated UIMA-1197: - defer past 2.3.0 cleanup - replace StringBuffer with StringBuilder in those cases where synchronization is not needed Key: UIMA-1197 URL: https://issues.apache.org/jira/browse/UIMA-1197 Project: UIMA Issue Type: Improvement Components: Collection Processing, Core Java Framework Affects Versions: 2.2.2 Reporter: Marshall Schor Priority: Minor -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: source files packaging
On Aug 28, 2009, at 3:14 PM, Marshall Schor wrote: We could do this for all of our Jars, and I'm thinking this would be a good idea. One reason would be it would align us slightly better with the maven way of doing things. When users download jars from maven they would find the sources rather than get maven warning messages that no sources were found, and the m2eclipse plugin would easily be able to get the sources. +1 Yes I would really appreciate having the source code in eclipse linked to the uiima jars automatically with mvn eclipse:eclipse. Jörn
[jira] Closed: (UIMA-1121) SimpleRunCPE exits with an error code on normal termination
[ https://issues.apache.org/jira/browse/UIMA-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor closed UIMA-1121. Resolution: Won't Fix Leaving the way it is, because of comment above in the Jira. SimpleRunCPE exits with an error code on normal termination --- Key: UIMA-1121 URL: https://issues.apache.org/jira/browse/UIMA-1121 Project: UIMA Issue Type: Bug Components: Examples Affects Versions: 2.2.2 Reporter: Aaron Kaplan Priority: Minor runCPE.sh is terminating with exit code 1 even when, as far as I can tell, everything went fine. Based on a quick look at SimpleRunCPE.java, I think collectionProcessComplete() ought to end with System.exit(0), rather than 1. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1090) Add tooling to measure things for tuning space/time
[ https://issues.apache.org/jira/browse/UIMA-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor updated UIMA-1090: - Affects Version/s: 2.3 Defer past 2.3.0 Add tooling to measure things for tuning space/time --- Key: UIMA-1090 URL: https://issues.apache.org/jira/browse/UIMA-1090 Project: UIMA Issue Type: Improvement Components: Core Java Framework Affects Versions: 2.2.2, 2.3 Reporter: Marshall Schor Priority: Minor Some fairly simple tooling could help users discover easy things to do to tune their UIMA application. One such tool might measure the % of space in the CAS used by unused features. This might occur when using a general component that could set many feature fields, but intentionally running it in a mode where many of the fields are unused. In this case, changing the type definition to exclude those fields would save space in the CAS, which could be significant in those cases where a lot of instances of those types are created (e.g., tokens). Such a tool could be packaged as a JMX measurement, or as a special annotator, or as some new part of the framework. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1089) Space/Time tradeoffs in the CAS
[ https://issues.apache.org/jira/browse/UIMA-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor updated UIMA-1089: - Affects Version/s: 2.3 defer beyond 2.3.0 Space/Time tradeoffs in the CAS --- Key: UIMA-1089 URL: https://issues.apache.org/jira/browse/UIMA-1089 Project: UIMA Issue Type: Improvement Components: Core Java Framework Affects Versions: 2.2.2, 2.3 Reporter: Marshall Schor Priority: Minor Investigate / implement optimizations that trade user-controllable time (running the optimizations) for space. One such optimization could be: sharing strings. To do the sharing requires additional computation and (temporary) storage to detect the sharing opportunities, but results in space savings. For instance, a common annotation might assign short strings like noun to a part-of-speech feature. If you are processing a large document, there may be a large number of these kinds of string valued features, picked from a small pool of allowable values. The CAS's string storage might be able to be optimized to share the string references in this case, at a cost of temporarily creating a hash table of the unique strings and using it to identify sharing possibilities. A new API call to do this optimization would isolate the performance/space overhead of doing this optimization to just those users and times where it makes sense to do this. An alternative would be to automatically figure this out for some selected kinds of optimizations, but I'm not sure that could be done without impacting finely-tuned systems negatively. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1088) Embeddability: restrict the amount of memory UIMA processing uses
[ https://issues.apache.org/jira/browse/UIMA-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor updated UIMA-1088: - Affects Version/s: 2.3 defer past 2.3.0 Embeddability: restrict the amount of memory UIMA processing uses - Key: UIMA-1088 URL: https://issues.apache.org/jira/browse/UIMA-1088 Project: UIMA Issue Type: Improvement Components: Core Java Framework Affects Versions: 2.2.2, 2.3 Reporter: Marshall Schor Priority: Minor UIMA is sometimes embedded with other components all running inside one JVM. In this environment, it would be useful to limit the amount of heap space that UIMA applications consume, so the other applications can run effectively. Perhaps this can be accomplished in practice by having an additional parameter, max UIMA heap cells, or something similar. Other ideas? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1087) Embeddability: recover better from out-of-memory errors
[ https://issues.apache.org/jira/browse/UIMA-1087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor closed UIMA-1087. Resolution: Won't Fix for reasons cited by Thilo - instead of trying to recover, try and limit UIMA memory consumption - see linked issue Embeddability: recover better from out-of-memory errors --- Key: UIMA-1087 URL: https://issues.apache.org/jira/browse/UIMA-1087 Project: UIMA Issue Type: Improvement Components: Core Java Framework Affects Versions: 2.2.2 Reporter: Marshall Schor Priority: Minor I have heard reports that some embedders of UIMA run it in a separate process, because sometimes a large document or misbehaving annotator can use up all the java memory, resulting in an unrecoverable out-of-memory error that crashes the whole JVM. Investigate / implement ways that the framework might be able to more gracefully recover from this kind of error, without crashing the JVM.Please post ideas about how to do this as comments to this Jira. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1082) Improve JCas docs to recommend against depending on == JCas cover objects
[ https://issues.apache.org/jira/browse/UIMA-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor updated UIMA-1082: - Affects Version/s: 2.3 defer past 2.3.0 Improve JCas docs to recommend against depending on == JCas cover objects - Key: UIMA-1082 URL: https://issues.apache.org/jira/browse/UIMA-1082 Project: UIMA Issue Type: Improvement Components: Core Java Framework Affects Versions: 2.2.2, 2.3 Reporter: Marshall Schor Priority: Minor Update the JCas docs to recommend against depending on getting the same cover JCas object for cas objects, which won't happen in some configurations including remotes, and if JCas caching is turned off (a new configuration option). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1075) CDE cannot specify parameter overrides for collection readers in an aggregate
[ https://issues.apache.org/jira/browse/UIMA-1075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor updated UIMA-1075: - Affects Version/s: 2.3 defer past 2.3.0 CDE cannot specify parameter overrides for collection readers in an aggregate - Key: UIMA-1075 URL: https://issues.apache.org/jira/browse/UIMA-1075 Project: UIMA Issue Type: Bug Components: Eclipse plugins Affects Versions: 2.2.2, 2.3 Reporter: Marshall Schor Priority: Minor -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1080) [Patch] Wro ng usage of URL in XmiWriterCasConsumer
[ https://issues.apache.org/jira/browse/UIMA-1080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor updated UIMA-1080: - Affects Version/s: 2.3 defer past 2.3.0 [Patch] Wrong usage of URL in XmiWriterCasConsumer -- Key: UIMA-1080 URL: https://issues.apache.org/jira/browse/UIMA-1080 Project: UIMA Issue Type: Improvement Components: InternalTools Affects Versions: 2.2.2, 2.3 Reporter: Richard Eckart Priority: Minor Attachments: UIMA-1080.patch The XmiWriterCasConsumer wraps the value of SourceDocumentInformation.getUri() in an URL to extract the path. This only works if the value returned by getUri() is actually an URL starting with http, ftp or some other known protocol. It does not work if a framework user puts some self-defined URIs in there, such as annolab://default/myfile. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (UIMA-1058) synch issue in FSClassRegistry.generators
[ https://issues.apache.org/jira/browse/UIMA-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor reassigned UIMA-1058: Assignee: Marshall Schor synch issue in FSClassRegistry.generators - Key: UIMA-1058 URL: https://issues.apache.org/jira/browse/UIMA-1058 Project: UIMA Issue Type: Bug Components: Core Java Framework Affects Versions: 2.2.2 Reporter: Marshall Schor Assignee: Marshall Schor Priority: Minor Fix For: 2.3 Findbugs found wrong synch of generators field. Figure out right thing to synch on. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1058) synch issue in FSClassRegistry.generators
[ https://issues.apache.org/jira/browse/UIMA-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor closed UIMA-1058. Resolution: Fixed synch issue in FSClassRegistry.generators - Key: UIMA-1058 URL: https://issues.apache.org/jira/browse/UIMA-1058 Project: UIMA Issue Type: Bug Components: Core Java Framework Affects Versions: 2.2.2 Reporter: Marshall Schor Priority: Minor Fix For: 2.3 Findbugs found wrong synch of generators field. Figure out right thing to synch on. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1035) CDE support for envVarRef
[ https://issues.apache.org/jira/browse/UIMA-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor updated UIMA-1035: - Affects Version/s: 2.3 defer past 2.3.0 CDE support for envVarRef - Key: UIMA-1035 URL: https://issues.apache.org/jira/browse/UIMA-1035 Project: UIMA Issue Type: Improvement Components: Eclipse plugins Affects Versions: 2.2.2, 2.3 Reporter: Marshall Schor Priority: Minor The Component Descriptor Editor (CDE) has never supported envVarRef - this is the capability to have environmental variables substituted at read-time for certain parts of the descriptor. The CDE design philosophy is such that it attempts to validate Component Descriptors at edit time. Some compromise should be figured out so that users who are using envVarRef can get some value from the CDE, and furthermore, the CDE should not remove envVarRef elements from the descriptor. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
