[jira] [Commented] (JENA-1427) Add nextOrElse() method in ExtendedIterator

[Andy Seaborne (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276983#comment-16276983
 ] 

Andy Seaborne commented on JENA-1427:
-

{{nextOptional}} added for release 3.6.0.

Proposal: close this JIRA for now, see how {{nextOptional}} works out and 
revisit {{orElse*}} based on experience.

> Add nextOrElse() method in ExtendedIterator
> ---
>
> Key: JENA-1427
> URL: https://issues.apache.org/jira/browse/JENA-1427
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: Jena 3.5.0
>Reporter: Adam Jacobs
>Priority: Trivial
>  Labels: easytask
>
> Allow a functional approach for returning a default value or throwing a 
> custom exception from a Jena iterator.
> The following method may be added to the ExtendedIterator interface.
> {noformat}
> /**
>  Answer the next object, if it exists, otherwise invoke the 
> _supplier_.
>  */
> public default T nextOrElse( Supplier supplier ) {
> return hasNext() ? next() : supplier.get();
> }
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (JENA-1427) Add nextOrElse() method in ExtendedIterator

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276959#comment-16276959
 ] 

ASF GitHub Bot commented on JENA-1427:
--

Github user ajs6f commented on the issue:

https://github.com/apache/jena/pull/323
  
Okay, that works for me!


> Add nextOrElse() method in ExtendedIterator
> ---
>
> Key: JENA-1427
> URL: https://issues.apache.org/jira/browse/JENA-1427
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: Jena 3.5.0
>Reporter: Adam Jacobs
>Priority: Trivial
>  Labels: easytask
>
> Allow a functional approach for returning a default value or throwing a 
> custom exception from a Jena iterator.
> The following method may be added to the ExtendedIterator interface.
> {noformat}
> /**
>  Answer the next object, if it exists, otherwise invoke the 
> _supplier_.
>  */
> public default T nextOrElse( Supplier supplier ) {
> return hasNext() ? next() : supplier.get();
> }
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] jena issue #323: JENA-1427: ExtendedIterator.nextOptional

[ajs6f]

Github user ajs6f commented on the issue:

https://github.com/apache/jena/pull/323
  
Okay, that works for me!


---

[jira] [Commented] (JENA-1427) Add nextOrElse() method in ExtendedIterator

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276956#comment-16276956
 ] 

ASF subversion and git services commented on JENA-1427:
---

Commit e512f51b10c479fa8fb24573d7b9112cde8e0fda in jena's branch 
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=e512f51 ]

JENA-1427: Merge commit 'refs/pull/323/head' of github.com:apache/jena

This closes #323.


> Add nextOrElse() method in ExtendedIterator
> ---
>
> Key: JENA-1427
> URL: https://issues.apache.org/jira/browse/JENA-1427
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: Jena 3.5.0
>Reporter: Adam Jacobs
>Priority: Trivial
>  Labels: easytask
>
> Allow a functional approach for returning a default value or throwing a 
> custom exception from a Jena iterator.
> The following method may be added to the ExtendedIterator interface.
> {noformat}
> /**
>  Answer the next object, if it exists, otherwise invoke the 
> _supplier_.
>  */
> public default T nextOrElse( Supplier supplier ) {
> return hasNext() ? next() : supplier.get();
> }
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (JENA-1427) Add nextOrElse() method in ExtendedIterator

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276955#comment-16276955
 ] 

ASF subversion and git services commented on JENA-1427:
---

Commit 084a5d9c11c672cc75617aadfeb39be317240625 in jena's branch 
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=084a5d9 ]

JENA-1427: ExtendedIterator.nextOptional


> Add nextOrElse() method in ExtendedIterator
> ---
>
> Key: JENA-1427
> URL: https://issues.apache.org/jira/browse/JENA-1427
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: Jena 3.5.0
>Reporter: Adam Jacobs
>Priority: Trivial
>  Labels: easytask
>
> Allow a functional approach for returning a default value or throwing a 
> custom exception from a Jena iterator.
> The following method may be added to the ExtendedIterator interface.
> {noformat}
> /**
>  Answer the next object, if it exists, otherwise invoke the 
> _supplier_.
>  */
> public default T nextOrElse( Supplier supplier ) {
> return hasNext() ? next() : supplier.get();
> }
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (JENA-1427) Add nextOrElse() method in ExtendedIterator

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276957#comment-16276957
 ] 

ASF GitHub Bot commented on JENA-1427:
--

Github user asfgit closed the pull request at:

https://github.com/apache/jena/pull/323


> Add nextOrElse() method in ExtendedIterator
> ---
>
> Key: JENA-1427
> URL: https://issues.apache.org/jira/browse/JENA-1427
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: Jena 3.5.0
>Reporter: Adam Jacobs
>Priority: Trivial
>  Labels: easytask
>
> Allow a functional approach for returning a default value or throwing a 
> custom exception from a Jena iterator.
> The following method may be added to the ExtendedIterator interface.
> {noformat}
> /**
>  Answer the next object, if it exists, otherwise invoke the 
> _supplier_.
>  */
> public default T nextOrElse( Supplier supplier ) {
> return hasNext() ? next() : supplier.get();
> }
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] jena pull request #323: JENA-1427: ExtendedIterator.nextOptional

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/jena/pull/323


---

[jira] [Commented] (JENA-1427) Add nextOrElse() method in ExtendedIterator

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276953#comment-16276953
 ] 

ASF GitHub Bot commented on JENA-1427:
--

Github user afs commented on the issue:

https://github.com/apache/jena/pull/323
  
That was already the case in the PR and I've added text to call it out 
explicitly into the javadoc.


> Add nextOrElse() method in ExtendedIterator
> ---
>
> Key: JENA-1427
> URL: https://issues.apache.org/jira/browse/JENA-1427
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: Jena 3.5.0
>Reporter: Adam Jacobs
>Priority: Trivial
>  Labels: easytask
>
> Allow a functional approach for returning a default value or throwing a 
> custom exception from a Jena iterator.
> The following method may be added to the ExtendedIterator interface.
> {noformat}
> /**
>  Answer the next object, if it exists, otherwise invoke the 
> _supplier_.
>  */
> public default T nextOrElse( Supplier supplier ) {
> return hasNext() ? next() : supplier.get();
> }
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] jena issue #323: JENA-1427: ExtendedIterator.nextOptional

[afs]

Github user afs commented on the issue:

https://github.com/apache/jena/pull/323
  
That was already the case in the PR and I've added text to call it out 
explicitly into the javadoc.


---

[jira] [Commented] (JENA-1440) Map ByteBuffer direct to NodeIds, avoiding a Record object (TupleIndexRecord)

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276873#comment-16276873
 ] 

ASF GitHub Bot commented on JENA-1440:
--

Github user afs commented on the issue:

https://github.com/apache/jena/pull/317
  
I had time for some more testing.


> Map ByteBuffer direct to NodeIds, avoiding a Record object (TupleIndexRecord)
> -
>
> Key: JENA-1440
> URL: https://issues.apache.org/jira/browse/JENA-1440
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: TDB2
>Affects Versions: Jena 3.5.0, Jena 3.6.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.6.0
>
>
> Avoiding going {{bytes-> Record->Tuple}} can save about 25% of time 
> in a large index scan (but there are lots of other things going on in a 
> typical query and this change would be negligible).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (JENA-1443) GraphView to provide graph transactions

[Andy Seaborne (JIRA)]

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

Andy Seaborne resolved JENA-1443.
-
Resolution: Done

> GraphView to provide graph transactions
> ---
>
> Key: JENA-1443
> URL: https://issues.apache.org/jira/browse/JENA-1443
> Project: Apache Jena
>  Issue Type: Improvement
>Affects Versions: Jena 3.5.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
> Fix For: Jena 3.6.0
>
>
> {{GraphView}} can provide a {{TransactionHandler}} that uses the underlying 
> {{DatasetGraph}}. Then some level of graph transaction support can be 
> provided.
> Due to the contract for {{begin()}}, this will have to be conservatively a 
> write transaction for the moment.  TDB2 already has R->W promotion enabled. 
> This could be rolled out to other datasets with necessary testing.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] jena issue #317: JENA-1440: TDB2 - transform bytes to NodeIds directly.

[afs]

Github user afs commented on the issue:

https://github.com/apache/jena/pull/317
  
I had time for some more testing.


---

[jira] [Resolved] (JENA-1440) Map ByteBuffer direct to NodeIds, avoiding a Record object (TupleIndexRecord)

[Andy Seaborne (JIRA)]

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

Andy Seaborne resolved JENA-1440.
-
   Resolution: Done
Fix Version/s: (was: Jena 3.7.0)
   Jena 3.6.0

> Map ByteBuffer direct to NodeIds, avoiding a Record object (TupleIndexRecord)
> -
>
> Key: JENA-1440
> URL: https://issues.apache.org/jira/browse/JENA-1440
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: TDB2
>Affects Versions: Jena 3.5.0, Jena 3.6.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.6.0
>
>
> Avoiding going {{bytes-> Record->Tuple}} can save about 25% of time 
> in a large index scan (but there are lots of other things going on in a 
> typical query and this change would be negligible).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (JENA-1443) GraphView to provide graph transactions

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276864#comment-16276864
 ] 

ASF subversion and git services commented on JENA-1443:
---

Commit 168588593b071f5351fef63566498be0a931ebdd in jena's branch 
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=1685885 ]

JENA-1443: Merge commit 'refs/pull/324/head' of github.com:apache/jena

This closes #324.


> GraphView to provide graph transactions
> ---
>
> Key: JENA-1443
> URL: https://issues.apache.org/jira/browse/JENA-1443
> Project: Apache Jena
>  Issue Type: Improvement
>Affects Versions: Jena 3.5.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
> Fix For: Jena 3.6.0
>
>
> {{GraphView}} can provide a {{TransactionHandler}} that uses the underlying 
> {{DatasetGraph}}. Then some level of graph transaction support can be 
> provided.
> Due to the contract for {{begin()}}, this will have to be conservatively a 
> write transaction for the moment.  TDB2 already has R->W promotion enabled. 
> This could be rolled out to other datasets with necessary testing.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (JENA-1440) Map ByteBuffer direct to NodeIds, avoiding a Record object (TupleIndexRecord)

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276865#comment-16276865
 ] 

ASF subversion and git services commented on JENA-1440:
---

Commit 52a9f02b94ebc351a17b6da16074a7b98e38d99a in jena's branch 
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=52a9f02 ]

JENA-1440: Merge commit 'refs/pull/317/head' of github.com:apache/jena

This closes #317.


> Map ByteBuffer direct to NodeIds, avoiding a Record object (TupleIndexRecord)
> -
>
> Key: JENA-1440
> URL: https://issues.apache.org/jira/browse/JENA-1440
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: TDB2
>Affects Versions: Jena 3.5.0, Jena 3.6.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.6.0
>
>
> Avoiding going {{bytes-> Record->Tuple}} can save about 25% of time 
> in a large index scan (but there are lots of other things going on in a 
> typical query and this change would be negligible).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (JENA-1440) Map ByteBuffer direct to NodeIds, avoiding a Record object (TupleIndexRecord)

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276866#comment-16276866
 ] 

ASF GitHub Bot commented on JENA-1440:
--

Github user asfgit closed the pull request at:

https://github.com/apache/jena/pull/317


> Map ByteBuffer direct to NodeIds, avoiding a Record object (TupleIndexRecord)
> -
>
> Key: JENA-1440
> URL: https://issues.apache.org/jira/browse/JENA-1440
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: TDB2
>Affects Versions: Jena 3.5.0, Jena 3.6.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.6.0
>
>
> Avoiding going {{bytes-> Record->Tuple}} can save about 25% of time 
> in a large index scan (but there are lots of other things going on in a 
> typical query and this change would be negligible).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (JENA-1443) GraphView to provide graph transactions

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276863#comment-16276863
 ] 

ASF subversion and git services commented on JENA-1443:
---

Commit abfb0530ff714b8d38d50ecbb3cb76f39087e6ad in jena's branch 
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=abfb053 ]

JENA-1443: Use DatasetGraph for GraphView TransactionHandler


> GraphView to provide graph transactions
> ---
>
> Key: JENA-1443
> URL: https://issues.apache.org/jira/browse/JENA-1443
> Project: Apache Jena
>  Issue Type: Improvement
>Affects Versions: Jena 3.5.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
> Fix For: Jena 3.6.0
>
>
> {{GraphView}} can provide a {{TransactionHandler}} that uses the underlying 
> {{DatasetGraph}}. Then some level of graph transaction support can be 
> provided.
> Due to the contract for {{begin()}}, this will have to be conservatively a 
> write transaction for the moment.  TDB2 already has R->W promotion enabled. 
> This could be rolled out to other datasets with necessary testing.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (JENA-1443) GraphView to provide graph transactions

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276867#comment-16276867
 ] 

ASF GitHub Bot commented on JENA-1443:
--

Github user asfgit closed the pull request at:

https://github.com/apache/jena/pull/324


> GraphView to provide graph transactions
> ---
>
> Key: JENA-1443
> URL: https://issues.apache.org/jira/browse/JENA-1443
> Project: Apache Jena
>  Issue Type: Improvement
>Affects Versions: Jena 3.5.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
> Fix For: Jena 3.6.0
>
>
> {{GraphView}} can provide a {{TransactionHandler}} that uses the underlying 
> {{DatasetGraph}}. Then some level of graph transaction support can be 
> provided.
> Due to the contract for {{begin()}}, this will have to be conservatively a 
> write transaction for the moment.  TDB2 already has R->W promotion enabled. 
> This could be rolled out to other datasets with necessary testing.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] jena pull request #324: JENA-1443: Use DatasetGraph for GraphView Transactio...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/jena/pull/324


---

[GitHub] jena pull request #317: JENA-1440: TDB2 - transform bytes to NodeIds directl...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/jena/pull/317


---

[jira] [Commented] (JENA-1436) RDFConnection does not implement Closable interface

[Andy Seaborne (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276854#comment-16276854
 ] 

Andy Seaborne commented on JENA-1436:
-

It's been a week so closing. Reopen for new information. 

> RDFConnection does not implement Closable interface
> ---
>
> Key: JENA-1436
> URL: https://issues.apache.org/jira/browse/JENA-1436
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: Jena
>Affects Versions: Jena 3.5.0
>Reporter: Claude Warren
>Priority: Minor
>
> RDFConnection implements the java.lang.AutoClosable interface but not the 
> java.io.Closable interface.  As such the apache IOUtils.closeQuietly() does 
> not work with an RDFConnection object.  I think that RDFConnection meets the 
> requirements for Closable namely
> A  Closable is a source or destination of data that can be closed.
> The close method is invoked to release resources that the object is
>  holding (such as open files).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (JENA-1436) RDFConnection does not implement Closable interface

[Andy Seaborne (JIRA)]

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

Andy Seaborne closed JENA-1436.
---
Resolution: Won't Fix

> RDFConnection does not implement Closable interface
> ---
>
> Key: JENA-1436
> URL: https://issues.apache.org/jira/browse/JENA-1436
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: Jena
>Affects Versions: Jena 3.5.0
>Reporter: Claude Warren
>Priority: Minor
>
> RDFConnection implements the java.lang.AutoClosable interface but not the 
> java.io.Closable interface.  As such the apache IOUtils.closeQuietly() does 
> not work with an RDFConnection object.  I think that RDFConnection meets the 
> requirements for Closable namely
> A  Closable is a source or destination of data that can be closed.
> The close method is invoked to release resources that the object is
>  holding (such as open files).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: CMS diff: Jena Full Text Search

[Andy Seaborne]

Changes applied and on jena.staging.apache.org.

Thank you

Andy



On 02/12/17 19:26, Andy Seaborne wrote:



On 01/12/17 16:26, Chris Tomlinson wrote:

Hi Andy,

The current commit is cumulative. The commit just prior to this one 
addressed all of Osma’s comments - which included my raising JENA-1437 
 and JENA-1438 
. This commit 
contains my changes to reflect those two issues as being fixed along 
with all my prior updates.


If there is a better procedure for making a series of updates to docs 
under CMS I’m happy to learn.


This is fine - I was checking it was what it looked like before applying 
it due to limited familiarity with the text indexing.


     Andy



Thank you for your help with this,
Chris



On Dec 1, 2017, at 6:10 AM, Andy Seaborne  wrote:

Chris - does this contain the previous one?

If so, are Osma's comments resolved?

If it's all good to go, I'll apply it because chnages can continue 
and are not frozen on a release.  I haven't had the time to check 
through the proposed changes and I'm not deeply familiar with the 
text indexing so I'm relying on others to verify them.


    Andy

On 30/11/17 17:28, Chris Tomlinson wrote:
This commit updates the jena-text documentation to be consistent 
with the resolved JENA-1437 and JENA-1438 issues.

Regards,
Chris
On Nov 30, 2017, at 5:00 PM, Chris Tomlinson  
wrote:


Clone URL (Committers only):
https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://jena.apache.org/documentation%2Fquery%2Ftext-query.mdtext 



Chris Tomlinson

Index: trunk/content/documentation/query/text-query.mdtext
===
--- trunk/content/documentation/query/text-query.mdtext
(revision 1816662)
+++ trunk/content/documentation/query/text-query.mdtext    (working 
copy)

@@ -1,5 +1,7 @@
Title: Jena Full Text Search

+Title: Jena Full Text Search
+
This extension to ARQ combines SPARQL and full text search via
[Lucene](https://lucene.apache.org) 6.4.1 or
[ElasticSearch](https://www.elastic.co) 5.2.1 (which is built on
@@ -64,7 +66,21 @@
## Table of Contents

-   [Architecture](#architecture)
+    -   [External content](#external-content)
+    -   [External applications](#external-applications)
+    -   [Document structure](#document-structure)
-   [Query with SPARQL](#query-with-sparql)
+    -   [Syntax](#syntax)
+    -   [Input arguments](#input-arguments)
+    -   [Output arguments](#output-arguments)
+    -   [Query strings](#query-strings)
+    -   [Simple queries](#simple-queries)
+    -   [Queries with language tags](#queries-with-language-tags)
+    -   [Queries that retrieve 
literals](#queries-that-retrieve-literals)

+    -   [Queries with graphs](#queries-with-graphs)
+    -   [Queries across multiple 
`Fields`](#queries-across-multiple-fields)
+    -   [Queries with _Boolean Operators_ and _Term 
Modifiers_](#queries-with-boolean-operators-and-term-modifiers)

+    -   [Good practice](#good-practice)
-   [Configuration](#configuration)
 -   [Text Dataset Assembler](#text-dataset-assembler)
 -   [Configuring an analyzer](#configuring-an-analyzer)
@@ -108,6 +124,7 @@

The text index uses the native query language of the index:
[Lucene query 
language](http://lucene.apache.org/core/6_4_1/queryparser/org/apache/lucene/queryparser/classic/package-summary.html#package_description) 


+(with [restrictions](#input-arguments))
or
[Elasticsearch query 
language](https://www.elastic.co/guide/en/elasticsearch/reference/5.2/query-dsl.html). 



@@ -134,6 +151,64 @@
By using Elasticsearch, other applications can share the text index 
with

SPARQL search.

+### Document structure
+
+As mentioned above, text indexing of a triple involves associating 
a Lucene

+document with the triple. How is this done?
+
+Lucene documents are composed of `Field`s. Indexing and searching 
are performed
+over the contents of these `Field`s. For an RDF triple to be 
indexed in Lucene the

+_property_ of the triple must be
+[configured in the entity map of a 
TextIndex](#entity-map-definition).
+This associates a Lucene analyzer with the _`property`_ which will 
be used
+for indexing and search. The _`property`_ becomes the _searchable_ 
Lucene

+`Field` in the resulting document.
+
+A Lucene index includes a _default_ `Field`, which is specified in 
the configuration,
+that is the field to search if not otherwise named in the query. 
In jena-text
+this field is configured via the `text:defaultField` property 
which is then mapped
+to a specific RDF property via `text:predicate` (see [entity 
map](#entity-map-definition)

+below).
+
+There are several additional `Field`s that will be included in the
+document that is passed to the Lucene `IndexWriter` depending on the
+configuration options that are used. These additional fields are 
used to

+manage the interface betwee

[jira] [Resolved] (JENA-1426) jena-text documentation corrections and clarifications

[Andy Seaborne (JIRA)]

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

Andy Seaborne resolved JENA-1426.
-
   Resolution: Done
Fix Version/s: Jena 3.6.0

> jena-text documentation corrections and clarifications
> --
>
> Key: JENA-1426
> URL: https://issues.apache.org/jira/browse/JENA-1426
> Project: Apache Jena
>  Issue Type: Documentation
>  Components: Jena
>Affects Versions: Jena 3.5.0
>Reporter: Code Ferret
>Assignee: Code Ferret
>Priority: Minor
>  Labels: documentation
> Fix For: Jena 3.6.0
>
> Attachments: text-query.mdtext.zip
>
>
> Upon reviewing [JENA-1388|https://issues.apache.org/jira/browse/JENA-1388], I 
> realized that the updates to the 
> [jena-text|https://jena.apache.org/documentation/query/text-query.html] 
> documentation that I prepared for 
> [JENA-1326|https://issues.apache.org/jira/browse/JENA-1326] were rather 
> incomplete and in one case incorrect. I'm opening this issue so that updated 
> documentation can be attached.
> The attached update to text-query.mdtext attempts to clarify how to use the 
> jena-text integration of Lucene as well as to demonstrate that there is no 
> loss of functionality of the integration versus direct Lucene queries, which 
> should obviate any need for extensions of the sort contemplated in 
> [JENA-1388|https://issues.apache.org/jira/browse/JENA-1388].



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (JENA-1426) jena-text documentation corrections and clarifications

[Andy Seaborne (JIRA)]

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

Andy Seaborne reassigned JENA-1426:
---

Assignee: Code Ferret

> jena-text documentation corrections and clarifications
> --
>
> Key: JENA-1426
> URL: https://issues.apache.org/jira/browse/JENA-1426
> Project: Apache Jena
>  Issue Type: Documentation
>  Components: Jena
>Affects Versions: Jena 3.5.0
>Reporter: Code Ferret
>Assignee: Code Ferret
>Priority: Minor
>  Labels: documentation
> Attachments: text-query.mdtext.zip
>
>
> Upon reviewing [JENA-1388|https://issues.apache.org/jira/browse/JENA-1388], I 
> realized that the updates to the 
> [jena-text|https://jena.apache.org/documentation/query/text-query.html] 
> documentation that I prepared for 
> [JENA-1326|https://issues.apache.org/jira/browse/JENA-1326] were rather 
> incomplete and in one case incorrect. I'm opening this issue so that updated 
> documentation can be attached.
> The attached update to text-query.mdtext attempts to clarify how to use the 
> jena-text integration of Lucene as well as to demonstrate that there is no 
> loss of functionality of the integration versus direct Lucene queries, which 
> should obviate any need for extensions of the sort contemplated in 
> [JENA-1388|https://issues.apache.org/jira/browse/JENA-1388].



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (JENA-478) Provide graceful server shutdown

[Andy Seaborne (JIRA)]

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

Andy Seaborne closed JENA-478.
--

> Provide graceful server shutdown
> 
>
> Key: JENA-478
> URL: https://issues.apache.org/jira/browse/JENA-478
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: Fuseki
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>
> (on the road to reconfigurtation of a running server)
> In the short term, this will improve testing by enabling clean servers to be 
> started and stopped.
> Deregistation includes deregistering datasets and removing their JMX bean for 
> the dataset (stats counters) as well as generally clearing up so that a 
> dataset of the same name can be added later.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (JENA-478) Provide graceful server shutdown

[Andy Seaborne (JIRA)]

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

Andy Seaborne resolved JENA-478.

Resolution: Not A Problem

Nowadays, with fully transactional datasets, there is no clean-shutdown 
requirements.

> Provide graceful server shutdown
> 
>
> Key: JENA-478
> URL: https://issues.apache.org/jira/browse/JENA-478
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: Fuseki
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>
> (on the road to reconfigurtation of a running server)
> In the short term, this will improve testing by enabling clean servers to be 
> started and stopped.
> Deregistation includes deregistering datasets and removing their JMX bean for 
> the dataset (stats counters) as well as generally clearing up so that a 
> dataset of the same name can be added later.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (JENA-458) Make model work across transaction boundaries / make model.begin do something reasonable.

[Andy Seaborne (JIRA)]

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

Andy Seaborne resolved JENA-458.

   Resolution: Done
Fix Version/s: Jena 3.6.0

Full model-across-transaction boundaries is in TDB2.

{{Model.begin}} over transactional datasets  works for JENA-1443 / PR#324.


> Make model work across transaction boundaries / make model.begin do something 
> reasonable.
> -
>
> Key: JENA-458
> URL: https://issues.apache.org/jira/browse/JENA-458
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: TDB
>Affects Versions: TDB 0.10.1
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.6.0
>
>
> Currently, the model view must be re-feteched from the TDB dataset across 
> transaction boundaries even if all updates went via the model.
> For some models, this is expensive - for example, inference models with 
> significant forward chaining.
> A problem will always be that if the database can change via a different 
> route.
> A side-effect will be that model.begin()/model.commit()/model.abort() can be 
> implemented as always being a write transaction.  It would need an API change 
> to support the difference between read and write.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (JENA-1426) jena-text documentation corrections and clarifications

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276821#comment-16276821
 ] 

ASF subversion and git services commented on JENA-1426:
---

Commit 1817093 from [~andy.seaborne] in branch 'site/trunk'
[ https://svn.apache.org/r1817093 ]

JENA-1426: Updates to jena-text documentation

> jena-text documentation corrections and clarifications
> --
>
> Key: JENA-1426
> URL: https://issues.apache.org/jira/browse/JENA-1426
> Project: Apache Jena
>  Issue Type: Documentation
>  Components: Jena
>Affects Versions: Jena 3.5.0
>Reporter: Code Ferret
>Priority: Minor
>  Labels: documentation
> Attachments: text-query.mdtext.zip
>
>
> Upon reviewing [JENA-1388|https://issues.apache.org/jira/browse/JENA-1388], I 
> realized that the updates to the 
> [jena-text|https://jena.apache.org/documentation/query/text-query.html] 
> documentation that I prepared for 
> [JENA-1326|https://issues.apache.org/jira/browse/JENA-1326] were rather 
> incomplete and in one case incorrect. I'm opening this issue so that updated 
> documentation can be attached.
> The attached update to text-query.mdtext attempts to clarify how to use the 
> jena-text integration of Lucene as well as to demonstrate that there is no 
> loss of functionality of the integration versus direct Lucene queries, which 
> should obviate any need for extensions of the sort contemplated in 
> [JENA-1388|https://issues.apache.org/jira/browse/JENA-1388].



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (JENA-1444) ASK queries return inconsistent results when contain blank nodes

[Andy Seaborne (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276617#comment-16276617
 ] 

Andy Seaborne commented on JENA-1444:
-

This test case includes {{OmQueryFactory}} which is not part of Jena.  As this 
class takes a string and produces a query, I suggest printing the query in the 
test to see if the query that has been built is as expected.

Testing with the current version of Jena would also be helpful.


> ASK queries return inconsistent results when contain blank nodes
> 
>
> Key: JENA-1444
> URL: https://issues.apache.org/jira/browse/JENA-1444
> Project: Apache Jena
>  Issue Type: Bug
>Affects Versions: Jena 3.3.0
>Reporter: Fabian Polkosnik
> Attachments: AskQueriesBug.java
>
>
> Execution of the same ASK query containing blank nodes might return different 
> results, depending on the set of provided prefixes.
> I attach a unit test which reproduces the issue.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (JENA-1444) ASK queries return inconsistent results when contain blank nodes

[Fabian Polkosnik (JIRA)]

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

Fabian Polkosnik updated JENA-1444:
---
Attachment: AskQueriesBug.java

> ASK queries return inconsistent results when contain blank nodes
> 
>
> Key: JENA-1444
> URL: https://issues.apache.org/jira/browse/JENA-1444
> Project: Apache Jena
>  Issue Type: Bug
>Affects Versions: Jena 3.3.0
>Reporter: Fabian Polkosnik
> Attachments: AskQueriesBug.java
>
>
> Execution of the same ASK query containing blank nodes might return different 
> results, depending on the set of provided prefixes.
> I attach a unit test which reproduces the issue.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (JENA-1444) ASK queries return inconsistent results when contain blank nodes

[Fabian Polkosnik (JIRA)]

Fabian Polkosnik created JENA-1444:
--

 Summary: ASK queries return inconsistent results when contain 
blank nodes
 Key: JENA-1444
 URL: https://issues.apache.org/jira/browse/JENA-1444
 Project: Apache Jena
  Issue Type: Bug
Affects Versions: Jena 3.3.0
Reporter: Fabian Polkosnik


Execution of the same ASK query containing blank nodes might return different 
results, depending on the set of provided prefixes.
I attach a unit test which reproduces the issue.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)