[GitHub] jena pull request: Update TextQueryPF.java

2015-05-26 Thread asfgit
Github user asfgit closed the pull request at:

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


---
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.
---


[GitHub] jena pull request: Update TextQueryPF.java

2015-05-26 Thread afs
Github user afs commented on the pull request:

https://github.com/apache/jena/pull/73#issuecomment-105658544
  
Thanks - PR merged.


---
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.
---


[GitHub] jena pull request: Update TextQueryPF.java

2015-05-26 Thread amiara514
GitHub user amiara514 opened a pull request:

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

Update TextQueryPF.java

A simple warning insertion about the comment : 
https://github.com/apache/jena/pull/64#issuecomment-105229534

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/73.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 #73


commit 1503c2597cd0d3294a2295699d71d1b5ae31e9f1
Author: Alexis Miara alexis_mi...@hotmail.com
Date:   2015-05-26T19:15:14Z

Update TextQueryPF.java

A simple warning insertion about the comment : 
https://github.com/apache/jena/pull/64#issuecomment-105229534




---
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] [Updated] (JENA-949) DISTINCT spilling to disk leads to wrong answers.

2015-05-26 Thread Andy Seaborne (JIRA)

 [ 
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 disk leads to wrong answers.  (was: DISTINCT 
spilling to disk leads to twrong answers.)

 DISTINCT spilling to disk 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

2015-05-26 Thread Ying Jiang
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?