On 24/06/15 15:39, Chris Dollin wrote:
In practice, the literal value would be stored using the Lucene
facility to
store the original field value alongside the indexed value
(TextField.TYPE_STORED). This would be similar to how LARQ worked. If the
langField setting was in use, the language
Hi all,
I would like to propose a new feature for jena-text, making it possible
to store the original literals in the Lucene index for fast retrieval.
I've talked about this before, but at that point it was difficult to
implement. With the recent jena-text work by Alexis Miara and myself, I
Hi all,
I tried to build the most recent jena-text module (without building any
other parts of Jena) but got these kind of errors:
[INFO] 20 errors
[INFO] -
[INFO]
On 24/06/15 13:00, Osma Suominen wrote:
Hi all,
I would like to propose a new feature for jena-text, making it possible to store
the original literals in the Lucene index for fast retrieval. I've talked about
this before, but at that point it was difficult to implement. With the recent
Oops, it turns out I had messed up my git clone and was using obsolete
code without realizing. Sorry for the noise.
-Osma
24.06.2015, 12:41, Osma Suominen kirjoitti:
Hi all,
I tried to build the most recent jena-text module (without building any
other parts of Jena) but got these kind of
[
https://issues.apache.org/jira/browse/JENA-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14600155#comment-14600155
]
Andy Seaborne commented on JENA-966:
There is no strategy to move
[
https://issues.apache.org/jira/browse/JENA-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14600105#comment-14600105
]
A. Soroka commented on JENA-974:
This sounds a lot like JENA-969. Perhaps we need a ticket
[
https://issues.apache.org/jira/browse/JENA-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14600157#comment-14600157
]
Andy Seaborne commented on JENA-974:
Temporary fix applied.
(I hope to find some time
[
https://issues.apache.org/jira/browse/JENA-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14600300#comment-14600300
]
Andy Seaborne commented on JENA-960:
Why have Jena-specific code to parse flags etc
[
https://issues.apache.org/jira/browse/JENA-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14600143#comment-14600143
]
ASF subversion and git services commented on JENA-974:
--
Commit
[
https://issues.apache.org/jira/browse/JENA-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14600108#comment-14600108
]
ASF subversion and git services commented on JENA-973:
--
Commit
[
https://issues.apache.org/jira/browse/JENA-974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-974.
Resolution: Fixed
Assignee: Andy Seaborne
Fix Version/s: Jena 3.0.0
[
https://issues.apache.org/jira/browse/JENA-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14599460#comment-14599460
]
A. Soroka commented on JENA-966:
That's very true-- I should not have been so brash about
On 24/06/15 16:21, Chris Dollin wrote:
Okay, but where should the type be stored in that case? In another field,
analoguous to langField?
Could use the same field with a flag for language vs type.
Right.
Since the field is already/currently intended for language tags, maybe
it could store
[
https://issues.apache.org/jira/browse/JENA-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14599460#comment-14599460
]
A. Soroka edited comment on JENA-966 at 6/24/15 2:10 PM:
-
That's
[
https://issues.apache.org/jira/browse/JENA-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14597501#comment-14597501
]
A. Soroka edited comment on JENA-966 at 6/24/15 2:07 PM:
-
I'm happy
[
https://issues.apache.org/jira/browse/JENA-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14597501#comment-14597501
]
A. Soroka edited comment on JENA-966 at 6/24/15 2:08 PM:
-
I'm happy
[
https://issues.apache.org/jira/browse/JENA-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14599547#comment-14599547
]
A. Soroka commented on JENA-966:
Is there any difference between {{LateBindingIterator}} and
[
https://issues.apache.org/jira/browse/JENA-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14599547#comment-14599547
]
A. Soroka edited comment on JENA-966 at 6/24/15 3:16 PM:
-
There is
[
https://issues.apache.org/jira/browse/JENA-973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-973:
---
Summary: Expression NOT EXISTS define equality by alegbra equivalence, not
syntax equivalance. (was:
[
https://issues.apache.org/jira/browse/JENA-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14599624#comment-14599624
]
A. Soroka commented on JENA-966:
As per comment on the dev mailing list, [~claudenw] is
On 24/06/15 13:51, Osma Suominen wrote:
On 24/06/15 15:39, Chris Dollin wrote:
In practice, the literal value would be stored using the Lucene
facility to
store the original field value alongside the indexed value
(TextField.TYPE_STORED). This would be similar to how LARQ worked. If the
[
https://issues.apache.org/jira/browse/JENA-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14599572#comment-14599572
]
Andy Seaborne commented on JENA-973:
The fix is to add {{Expr.equalsBySyntax}} in
[
https://issues.apache.org/jira/browse/JENA-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14599522#comment-14599522
]
A. Soroka commented on JENA-960:
Did we come to some conclusion about the direction of
[
https://issues.apache.org/jira/browse/JENA-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14599547#comment-14599547
]
A. Soroka edited comment on JENA-966 at 6/24/15 3:34 PM:
-
There is
Right, I updated my comment right after I made it, when I noticed the
difference.
I shouldn't think it matters which one to keep. LazyIterator is a little
shorter to write. :)
There are a number of other Iterators (noted in the comments to that ticket)
that seem to be depreciate-able. E.g.
[
https://issues.apache.org/jira/browse/JENA-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14599637#comment-14599637
]
A. Soroka commented on JENA-966:
[~andy.seaborne], I am still not clear about your objection
Yes. LazyIterator implements ExtendedIterator. LateBindingIterator
implements Iterator
My plan -- probably won't execute until tomorrow night -- is to complete
the implementation of LazyIterator for both (2.13.1 and 3.0.0) and then
deprecate LateBinding in favor of Lazy as ExtendedIterator
[
https://issues.apache.org/jira/browse/JENA-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14599851#comment-14599851
]
ASF GitHub Bot commented on JENA-966:
-
GitHub user ajs6f opened a pull request:
Github user ajs6f commented on the pull request:
https://github.com/apache/jena/pull/79#issuecomment-114963573
Closed in favor of #80 .
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user ajs6f commented on the pull request:
https://github.com/apache/jena/pull/79#issuecomment-114963486
Closed in favor of #80 .
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
A. Soroka created JENA-974:
--
Summary: jena-querybuilder cannot build
Key: JENA-974
URL: https://issues.apache.org/jira/browse/JENA-974
Project: Apache Jena
Issue Type: Bug
Components:
GitHub user ajs6f opened a pull request:
https://github.com/apache/jena/pull/80
Deprecating and removing some iterators from jena-core
https://issues.apache.org/jira/browse/JENA-966
You can merge this pull request into a Git repository by running:
$ git pull
[
https://issues.apache.org/jira/browse/JENA-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14599856#comment-14599856
]
ASF GitHub Bot commented on JENA-966:
-
Github user ajs6f commented on the pull request:
Github user ajs6f closed the pull request at:
https://github.com/apache/jena/pull/79
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled
[
https://issues.apache.org/jira/browse/JENA-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14599857#comment-14599857
]
ASF GitHub Bot commented on JENA-966:
-
Github user ajs6f closed the pull request at:
[
https://issues.apache.org/jira/browse/JENA-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14599853#comment-14599853
]
ASF GitHub Bot commented on JENA-966:
-
Github user ajs6f commented on the pull request:
[
https://issues.apache.org/jira/browse/JENA-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14600014#comment-14600014
]
A. Soroka commented on JENA-974:
Commit c6bf61d90b8f542d1fa186d045057141a8bf1e13 fails in
[
https://issues.apache.org/jira/browse/JENA-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14600063#comment-14600063
]
A. Soroka commented on JENA-974:
Commit 3033e44080509e7105e75773775fde20c377c2a1 fails in
39 matches
Mail list logo
