[jira] [Resolved] (JENA-950) Throw specific exception on lucene query string parse errors.
[
https://issues.apache.org/jira/browse/JENA-950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-950.
Resolution: Fixed
Fix Version/s: Jena 3.0.0
Throw specific exception on lucene query string parse errors.
-
Key: JENA-950
URL: https://issues.apache.org/jira/browse/JENA-950
Project: Apache Jena
Issue Type: Bug
Components: Fuseki, Text
Reporter: Andy Seaborne
Assignee: Andy Seaborne
Fix For: Jena 3.0.0
If left to a bland TextIndexException, Fuseki will generate a 500 (server
error due to runtime execution error) when it is really a client error 400
(bad request). While lucense query strings can be variables, this is very
unusual and still not server error.
Throw {{TextIndexParseException}}, subclass of {{QueryParseException}} to
differentiate internal errors and dynamic parse errors.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Fwd: Help with apache: Big data and apacheCon: Core
Is anyone here interested in pushing this forward. I have previously proposed a talk covering the design and implementation of the permissions module. Claude -- Forwarded message -- From: jan i j...@apache.org Date: Thu, May 28, 2015 at 7:58 PM Subject: Help with apache: Big data and apacheCon: Core To: apachecon-disc...@apache.org Dear PMC. We have just announced the call for Papers for apache Big data and apacheCon: Core. If your project would like a track (1 day == 6 presentations) or a half track (3 presentations), please contact me. Building a track (or half track) is a good way of securing (without guarantee) that your project is represented in the events. PMCs that suggest tracks (half tracks) for apacheCon: Core will decide the content, with only an outside oversight. We hope you will take the oppertunity and build an awesome track representing your projects. We are of course also open if a group of projects builds a track together. We hope to be able to make some cross project presentations/panels. An example is the future of web and web applications, many people ask if e.g. httpd and tomcat will play a major role in the future of internet. We hope some (especially the more mature projects) will grab the idea, and come with suggestions. Especially apacheCon: Core is open for innovation. Looking forward to help build super events with YOUR assistance. on behalf of the apacheCon team and LF jan I. -- I like: Like Like - The likeliest place on the web http://like-like.xenei.com LinkedIn: http://www.linkedin.com/in/claudewarren
[GitHub] jena pull request: Update TextDatasetFactory.java
GitHub user amiara514 opened a pull request: https://github.com/apache/jena/pull/74 Update TextDatasetFactory.java Reintroducing previous static methods for backward compatibility You can merge this pull request into a Git repository by running: $ git pull https://github.com/amiara514/jena patch-1 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/jena/pull/74.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #74 commit 8b9c0ffb39bd6b6f4df8f7c359491cde891e1788 Author: Alexis Miara alexis_mi...@hotmail.com Date: 2015-05-28T17:15:08Z Update TextDatasetFactory.java Reintroducing previous static methods for backward compatibility --- 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 but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (JENA-950) Throw specific exception on lucene query string parse errors.
[
https://issues.apache.org/jira/browse/JENA-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14563551#comment-14563551
]
ASF subversion and git services commented on JENA-950:
--
Commit 8c6e0b2aa5314cccd701fd47b08fff588a679009 in jena's branch
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=8c6e0b2 ]
JENA-950 : Specific TextIdexParseException
Throw specific exception on lucene query string parse errors.
-
Key: JENA-950
URL: https://issues.apache.org/jira/browse/JENA-950
Project: Apache Jena
Issue Type: Bug
Components: Fuseki, Text
Reporter: Andy Seaborne
Assignee: Andy Seaborne
If left to a bland TextIndexException, Fuseki will generate a 500 (server
error due to runtime execution error) when it is really a client error 400
(bad request). While lucense query strings can be variables, this is very
unusual and still not server error.
Throw {{TextIndexParseException}}, subclass of {{QueryParseException}} to
differentiate internal errors and dynamic parse errors.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (JENA-951) Throw specific exception on lucene query string parse errors.
Andy Seaborne created JENA-951:
--
Summary: Throw specific exception on lucene query string parse
errors.
Key: JENA-951
URL: https://issues.apache.org/jira/browse/JENA-951
Project: Apache Jena
Issue Type: Bug
Components: Fuseki, Text
Reporter: Andy Seaborne
Assignee: Andy Seaborne
If left to a bland TextIndexException, Fuseki will generate a 500 (server error
due to runtime execution error) when it is really a client error 400 (bad
request). While lucense query strings can be variables, this is very unusual
and still not server error.
Throw {{TextIndexParseException}}, subclass of {{QueryParseException}} to
differentiate internal errors and dynamic parse errors.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (JENA-950) Throw specific exception on lucene query string parse errors.
[
https://issues.apache.org/jira/browse/JENA-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14563550#comment-14563550
]
ASF subversion and git services commented on JENA-950:
--
Commit 7f806f737f217e0d8c60e751b47409b3d1ffdd11 in jena's branch
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=7f806f7 ]
JENA-950 : Generate bad request on runtime parser errors.
Throw specific exception on lucene query string parse errors.
-
Key: JENA-950
URL: https://issues.apache.org/jira/browse/JENA-950
Project: Apache Jena
Issue Type: Bug
Components: Fuseki, Text
Reporter: Andy Seaborne
Assignee: Andy Seaborne
If left to a bland TextIndexException, Fuseki will generate a 500 (server
error due to runtime execution error) when it is really a client error 400
(bad request). While lucense query strings can be variables, this is very
unusual and still not server error.
Throw {{TextIndexParseException}}, subclass of {{QueryParseException}} to
differentiate internal errors and dynamic parse errors.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (JENA-950) Throw specific exception on lucene query string parse errors.
[
https://issues.apache.org/jira/browse/JENA-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14563552#comment-14563552
]
ASF subversion and git services commented on JENA-950:
--
Commit e789e9f3d77d410cda0df03a270ff8d00948a375 in jena's branch
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=e789e9f ]
JENA-950 : Better error message.
Throw specific exception on lucene query string parse errors.
-
Key: JENA-950
URL: https://issues.apache.org/jira/browse/JENA-950
Project: Apache Jena
Issue Type: Bug
Components: Fuseki, Text
Reporter: Andy Seaborne
Assignee: Andy Seaborne
If left to a bland TextIndexException, Fuseki will generate a 500 (server
error due to runtime execution error) when it is really a client error 400
(bad request). While lucense query strings can be variables, this is very
unusual and still not server error.
Throw {{TextIndexParseException}}, subclass of {{QueryParseException}} to
differentiate internal errors and dynamic parse errors.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Deleted] (JENA-951) Throw specific exception on lucene query string parse errors.
[
https://issues.apache.org/jira/browse/JENA-951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne deleted JENA-951:
---
Throw specific exception on lucene query string parse errors.
-
Key: JENA-951
URL: https://issues.apache.org/jira/browse/JENA-951
Project: Apache Jena
Issue Type: Bug
Reporter: Andy Seaborne
Assignee: Andy Seaborne
If left to a bland TextIndexException, Fuseki will generate a 500 (server
error due to runtime execution error) when it is really a client error 400
(bad request). While lucense query strings can be variables, this is very
unusual and still not server error.
Throw {{TextIndexParseException}}, subclass of {{QueryParseException}} to
differentiate internal errors and dynamic parse errors.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (JENA-949) DISTINCT spilling to a data bag leads to wrong answers.
[
https://issues.apache.org/jira/browse/JENA-949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-949:
---
Summary: DISTINCT spilling to a data bag leads to wrong answers. (was:
DISTINCT spilling to disk leads to wrong answers.)
DISTINCT spilling to a data bag leads to wrong answers.
---
Key: JENA-949
URL: https://issues.apache.org/jira/browse/JENA-949
Project: Apache Jena
Issue Type: Bug
Components: ARQ
Affects Versions: Jena 3.0.0
Reporter: Andy Seaborne
Attachments: Jena949_1.java
In the attached example, the same query is made twice. The second time
{{ARQ.spillToDiskThreshold}} is set to 2L. The first results are correct.
[email
2015-05-20|http://mail-archives.apache.org/mod_mbox/jena-users/201505.mbox/%3C34B3B313-EAE4-4498-875F-A9674A8B3B2D%40interition.net%3E]
reports a possibly similar situation at scale.
The presence of {{DISTINCT}} is the key factor.
Output:
{noformat}
---
| g |
===
| http://example/g1 |
| http://example/g2 |
| http://example/g3 |
| http://example/g4 |
| http://example/g5 |
| http://example/g6 |
| http://example/g7 |
| http://example/g8 |
| http://example/g9 |
| http://example/g0 |
---
---
| g |
===
| http://example/g1 |
| http://example/g2 |
---
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (JENA-949) DISTINCT spilling to a data bag leads to wrong answers.
[
https://issues.apache.org/jira/browse/JENA-949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14562768#comment-14562768
]
Andy Seaborne commented on JENA-949:
Analysis:
The problem is that the return from the distinct data net is misused:
{code:title=QueryIterDistinct}
@Override
protected boolean isFreshSighting(Binding binding)
{
return db.netAdd(binding) ;
}
{code}
A return of true means definitely new, false covers two cases. While filling
the first part of the bag, the distinct data net returns false if the item is a
duplicate. Once it starts spilling, it returns false as an unknown always.
{{QueryIterDistinct}} does not go back to check the data bag when the input
iterator closes. What is more, some results have already been yielded so the
data bag iterator is the wrong answer.
The effect on {{QueryIterDistinct}} is that it will always skip over items
added to the spilled data.
DISTINCT spilling to a data bag leads to wrong answers.
---
Key: JENA-949
URL: https://issues.apache.org/jira/browse/JENA-949
Project: Apache Jena
Issue Type: Bug
Components: ARQ
Affects Versions: Jena 3.0.0
Reporter: Andy Seaborne
Attachments: Jena949_1.java
In the attached example, the same query is made twice. The second time
{{ARQ.spillToDiskThreshold}} is set to 2L. The first results are correct.
[email
2015-05-20|http://mail-archives.apache.org/mod_mbox/jena-users/201505.mbox/%3C34B3B313-EAE4-4498-875F-A9674A8B3B2D%40interition.net%3E]
reports a possibly similar situation at scale.
The presence of {{DISTINCT}} is the key factor.
Output:
{noformat}
---
| g |
===
| http://example/g1 |
| http://example/g2 |
| http://example/g3 |
| http://example/g4 |
| http://example/g5 |
| http://example/g6 |
| http://example/g7 |
| http://example/g8 |
| http://example/g9 |
| http://example/g0 |
---
---
| g |
===
| http://example/g1 |
| http://example/g2 |
---
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: [ANN] GSoC 2015 Accepts a Student Project for Jena
Hi,
Ying,
I'll stick to the list for discussion. Thanks for your guide! I
re-created a fresh new branch of JENA-491, which did not contain hp
package any more.
Andy,
You mention that the GRAPH grammar needs revisions. Please check the
following ones. I add the short form. Am I missing anything else?
Complete form:
CONSTRUCT {
# Named graph
GRAPH :g { ?s :p ?o }
# Default graph
{ ?s :p ?o }
# Named graph
:g { ?s :p ?o }
# Default graph
?s :p ?o
} WHERE { ... }
Short form:
CONSTRUCT {
} WHERE { ... }
regards,
Qihong
On Tue, May 26, 2015 at 11:12 PM, Ying Jiang jpz6311...@gmail.com wrote:
Hi Qihong,
As Andy mentioned, the bonding period is for community bonding, not
just mentor bonding. I can help you with JavaCC for the project. But
much more work needs comments and discussions with others in the
community. For example, Andy just pointed out the design issue and the
timeline changes. It's required for you to think about it and make
revisions accordingly. If any questions, just ask on the mailing list.
You'll get answers from the right one, not just from me.
It seems that your JENA-491 branch still uses com.hp.hpl.jena. Have
you re-checked out the latest code?
Best regards,
Ying Jiang
On Mon, May 25, 2015 at 11:10 PM, Andy Seaborne a...@apache.org wrote:
Hi Qihong,
One of the reasons there is a community bonding period is to create the
right social context for the work rather than just being about technical
work. As other people may be working on the areas you need to modify, this
will help avoid problems.
Discussions should be on this list and there has been nothing. Discussions
are also here to help you. It's a large codebase, and some of it quite old.
It makes it hard to see what's important and what's not.
When it comes to decisions, the Apache catchphrase is if it isn't on the
list, it does not exist. Given that the Jena development community only
exists via this list, you'll appreciate that this is quite important.
Please discuss with Ying about regular (minimum, weekly) on the list.
There are some changes to the plan if the javacc work is done first. Alos,
we have discussed a revised design with GRAPH inside the CONSTRUCT template.
Don't forget the case of CONSTRUCT WHERE { } shorthand form.
What does the timeline look like with these revisions? That changes the
Week 1 - Week 3 slot. Some of that freed up time should go to announcing
the changes on the users@ list, I suggest just after the mid term
evaluation.
You will have noticed that the package structure in ARQ has changed. There
is no com.hp.hpl.jena anymore, it's all moved under org.apache.jena. You
are probably better off starting from a clean clone of Jena.
Andy
On 24/05/15 14:12, Qihong Lin wrote:
Hi,
Sorry for my late response. During the community binding period, I
studied the JavaCC grammar with my mentor's help. Now, I know how to
use JavaCC in this project.
A new branch of JENA-491 [1] has just been set up. I'll code there in
the first place, and finally merge the code into jena master.
In all, I think everything is ready. Let's begin coding!
regards,
Qihong
[1] https://github.com/confidencesun/jena/tree/JENA-491
On Tue, May 19, 2015 at 4:55 AM, Andy Seaborne a...@apache.org wrote:
On 05/05/15 11:52, Andy Seaborne wrote:
On 28/04/15 13:09, Ying Jiang wrote:
Hi all,
FYI, Google announced the accepted projects of GSoC 2015 yesterday. A
Jena project of Extend CONSTRUCT to build quads (JENA-491) [1] is
among them.
Cheers,
Ying Jiang
[1]
https://docs.google.com/document/d/1KiDlfxMq5ZsU7vj7ZDm10yC96OZgdltwmZAZl56sTw0/edit#heading=h.fwbztdn0y3zl
Hi,
What's the plan for the bonding period?
Andy
Ping?
