[
https://issues.apache.org/jira/browse/JENA-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13398588#comment-13398588
]
Andy Seaborne commented on JENA-266:
------------------------------------
Yes, a bit spooky isn't? Jenkins seems to look at commit logs and poke JIRA
based on any JIRA label.
It is only the module build done, without deployment (left from when we built
things separately) - the whole of apache-jena is always and only built over
night. If a module changes an external interface, a manual "mvn clean deploy"
is needed.
Any Jena commiter can go into Jenkins and request a build immediately.
Jena is not a very large build (TDB is bit slow because of disk-based tests).
We could change to a a whole-system build after a commit.
> MINUS operations too slow
> -------------------------
>
> Key: JENA-266
> URL: https://issues.apache.org/jira/browse/JENA-266
> Project: Apache Jena
> Issue Type: Improvement
> Components: ARQ
> Reporter: Paul Gearon
> Assignee: Rob Vesse
> Attachments: arq.patch
>
>
> MINUS operations use an N^2 algorithm when evaluating. Despite the data being
> placed on the heap, an operating removing ~100k bindings from ~500k bindings
> takes >15 minutes on desktop systems (15 minutes being the time at which the
> process is killed. It may take significantly longer).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
