[jira] [Commented] (JENA-1414) Performance regression in Model.remove(Model m) method

[ https://issues.apache.org/jira/browse/JENA-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16259710#comment-16259710 ] ASF GitHub Bot commented on JENA-1414: -- Github user ajs6f commented on the issue:

[GitHub] jena issue #306: Algorithms for JENA-1414

Github user ajs6f commented on the issue: https://github.com/apache/jena/pull/306 Okay, now I get it. Agreed that number 3 is "trying too hard" and on the proposal to provide number 2 and document appropriate usage. ---

[jira] [Commented] (JENA-1414) Performance regression in Model.remove(Model m) method

[ https://issues.apache.org/jira/browse/JENA-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16259704#comment-16259704 ] ASF GitHub Bot commented on JENA-1414: -- Github user ajs6f commented on a diff in the p

[GitHub] jena pull request #306: Algorithms for JENA-1414

Github user ajs6f commented on a diff in the pull request: https://github.com/apache/jena/pull/306#discussion_r152085996 --- Diff: jena-core/src/main/java/org/apache/jena/graph/GraphUtil.java --- @@ -246,43 +282,214 @@ private static void deleteIteratorWorkerDirect(Graph graph, Ite

[jira] [Commented] (JENA-1430) Quad loading for in-memory assemblers

[ https://issues.apache.org/jira/browse/JENA-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16259653#comment-16259653 ] ASF GitHub Bot commented on JENA-1430: -- GitHub user ajs6f opened a pull request:

[GitHub] jena pull request #314: JENA-1430

GitHub user ajs6f opened a pull request: https://github.com/apache/jena/pull/314 JENA-1430 Includes #313, plus: - Extend testing to `DatasetAssembler` - Ensure that `DatasetAssembler` can also load quads - Correct `ja:DatasetTxnMem` => `ja:MemoryDataset` You can mer

[jira] [Commented] (JENA-1430) Quad loading for in-memory assemblers

[ https://issues.apache.org/jira/browse/JENA-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16259486#comment-16259486 ] A. Soroka commented on JENA-1430: - That definitely makes sense. We want people to be able t

[jira] [Commented] (JENA-1430) Quad loading for in-memory assemblers

[ https://issues.apache.org/jira/browse/JENA-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16259478#comment-16259478 ] Andy Seaborne commented on JENA-1430: - The document https://jena.apache.org/docume

Re: CMS diff: Jena Full Text Search

I went to review this diff and rediscovered (to my chagrin) that I really know very little about Jena's text indexing. Osma (or anyone else who knows text indexing better than do I, which wouldn't take much)-- could you review this? It's got some great useful detail about how the indexing works

Re: Issues fixed in Apache Jena

Comments inline: On 20/11/2017, 14:47, "Γεώργιος Δίγκας" wrote: Dear Andy and All, Thank you very much for the information that you have provided to me. You really helped me a lot. Below I list some of the most frequent issue types that I have found while I was examining the e

Re: Issues fixed in Apache Jena

Dear Andy and All, Thank you very much for the information that you have provided to me. You really helped me a lot. Below I list some of the most frequent issue types that I have found while I was examining the evolution of Jena. Issue Name Issues over timeFixed Currently Open T

[jira] [Commented] (JENA-1430) Quad loading for in-memory assemblers

[ https://issues.apache.org/jira/browse/JENA-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16259107#comment-16259107 ] ASF GitHub Bot commented on JENA-1430: -- GitHub user afs opened a pull request: ht

[GitHub] jena pull request #313: JENA-1430: Read quads for ja:data by filename

GitHub user afs opened a pull request: https://github.com/apache/jena/pull/313 JENA-1430: Read quads for ja:data by filename Add support for {{ja:data "filename"}}. Strings as filenames and URIs as file names resolve different (the JVM cwd and the assembler file location re

[jira] [Reopened] (JENA-1429) Error with # comments in SPARQL

[ https://issues.apache.org/jira/browse/JENA-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Vesse reopened JENA-1429: - > Error with # comments in SPARQL > --- > > Key: JENA-1429 >

[jira] [Resolved] (JENA-1429) Error with # comments in SPARQL

[ https://issues.apache.org/jira/browse/JENA-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Vesse resolved JENA-1429. - Resolution: Invalid > Error with # comments in SPARQL > --- > >

[jira] [Commented] (JENA-1429) Error with # comments in SPARQL

[ https://issues.apache.org/jira/browse/JENA-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16259056#comment-16259056 ] Andy Seaborne commented on JENA-1429: - You have to encode {{#}} marks the URI fragment.

Re: jena-project

+1 On 17/11/2017, 15:16, "ajs6f" wrote: I'm basically +1 to this-- jena-project was always confusing at best. In theory, we could factor out some of those 932 lines with a Jena Maven BOM. Actually, that might be nice for integrators and those using apache-jena-lib. ajs6f