[GitHub] [jena-site] kinow commented on pull request #133: main branch for Jena 4.7.0
kinow commented on PR #133: URL: https://github.com/apache/jena-site/pull/133#issuecomment-1359950734 I hope that doesn't complicate more the release process (mostly managed by you, thanks for that!) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: LATERAL
I take note of your keyword suggestion "LATERAL" vs "LATERAL JOIN". On Tue, Dec 20, 2022 at 6:01 PM Andy Seaborne wrote: > On 20/12/2022 17:24, Marco Neumann wrote: > > OK I will repeat this elsewhere again but as you are aware there was > > a good discussion on the SPARQL-12 list with plenty of suggestions. > > maybe something like Sideways Information Passing > > or correlate subquery join. > > Noting I didn't choose the name. > > The keyword is "LATERAL" not "LATERAL JOIN". > > (SIP is an implementation technique for joins - it is best if the > ordering of the left-right flow is "jump forwards") > > SQL has some several forms of correlated subquery. > > I see a suggestions - it's more like exploring the space - no consensus. > LATERAL is the one that examples come back to. > > The nearest seems to be FOR EACH but that isn't infix syntax which > causes more text. > > "flatMap" is not data-user friendly. > > > > Without nested results tables, it won't solve the general GraphQL case. > As per discussion. > > And nested results tables would be a whole different design. > > > > If variables must be named: > > 1: It is more work for the user in the common case. > > 2: Putting a projection in the subquery for the uncommon cases seems > better UX > > 3: What happens if a variable is not bound? > > 4: Not the same as EXISTS so no implementation sharing. > > Andy > > PS Historical note: > LATERAL is the semantics for SPARQL 1.0 LC1 > > -- --- Marco Neumann
LATERAL
On 20/12/2022 17:24, Marco Neumann wrote: > OK I will repeat this elsewhere again but as you are aware there was > a good discussion on the SPARQL-12 list with plenty of suggestions. > maybe something like Sideways Information Passing > or correlate subquery join. Noting I didn't choose the name. The keyword is "LATERAL" not "LATERAL JOIN". (SIP is an implementation technique for joins - it is best if the ordering of the left-right flow is "jump forwards") SQL has some several forms of correlated subquery. I see a suggestions - it's more like exploring the space - no consensus. LATERAL is the one that examples come back to. The nearest seems to be FOR EACH but that isn't infix syntax which causes more text. "flatMap" is not data-user friendly. Without nested results tables, it won't solve the general GraphQL case. As per discussion. And nested results tables would be a whole different design. If variables must be named: 1: It is more work for the user in the common case. 2: Putting a projection in the subquery for the uncommon cases seems better UX 3: What happens if a variable is not bound? 4: Not the same as EXISTS so no implementation sharing. Andy PS Historical note: LATERAL is the semantics for SPARQL 1.0 LC1
Re: [] Apache Jena 4.7.0 RC1
OK I will repeat this elsewhere again but as you are aware there was a good discussion on the SPARQL-12 list with plenty of suggestions. maybe something like Sideways Information Passing or correlated subquery join. I will end this thread here to allow the process to proceed. On Tue, Dec 20, 2022 at 5:06 PM Andy Seaborne wrote: > > On 20/12/2022 16:44, Marco Neumann wrote: > > The URL to Lateral Joins is broken > > https://jena.apache.org/documentation/query/lateral-join.html > > The web site is updated when the release happens after the VOTE. > > It is on the "lateral-doc" branch at the moment. > > But go to the SPARQL CG text. > > > Overall I think this is a good contribution but I am not happy with the > > name "LATERAL join" as it implies SQL LATERAL join similarities. Can we > > call this something else? > > Such as? > > --- > > It is not suddenly dropping into a release. > It is mentioned in email "Towards Jena 4.7.0" > It is https://github.com/apache/jena/issues/1615 > > And it says "This is an experimental feature." > > VOTE threads are first and foremost about process. > > --- > > This is a discussion for SPARQL CG: > > https://github.com/w3c/sparql-12/issues/100 > https://github.com/w3c/sparql-12/blob/main/SEP/SEP-0006/sep-0006.md > > It's not what I might call a "join" (evaluate left and right arguments, > then perform operation to combine the two sides) but SQL-terminolgy is > often to call it a "join". > > https://docs.snowflake.com/en/sql-reference/constructs/join-lateral.html > """ > for each row in left_hand_table LHT: > execute right_hand_subquery RHS using the values from the current > row in the LHT > """ > > Andy > > c.f. Oxigraph. > > > > > Thank you, > > Marco > > > > . > > > > On Tue, Dec 20, 2022 at 4:39 PM Andy Seaborne wrote: > > > >> Hi, > >> > >> Here is a vote on the release of Apache Jena 4.7.0. > >> This is the first release candidate. > >> > >> The deadline is > >> > >> Friday, 23rd December 2022 at 18:00 UTC > >> > >> Please vote to approve this release: > >> > >> [ ] +1 Approve the release > >> [ ] 0 Don't care > >> [ ] -1 Don't release, because ... > >> > >> Items in this release > >> > >> https://s.apache.org/jena-4.7.0-issues > >> > >> Major: > >> > >> * Lucene upgrade 8.11.1 to 9.4.1 - @OyvindLGjesdal > >> There are changes to the stopword setting in the default > >> configuration of Lucene's StandardAnalyzer > >> Issue: https://github.com/apache/jena/issues/1581 > >> PR: https://github.com/apache/jena/pull/1582 > >> > >> * LATERAL joins > >> This is an experimental feature. > >> Issue: https://github.com/apache/jena/issues/1615 > >> Documentation: > >> https://jena.apache.org/documentation/query/lateral-join.html > >> > >> * RDF Patch > >> https://lists.apache.org/thread/8oc1gn2qnzx4ddwovx8h545jm270gpyx > >> Issue: https://github.com/apache/jena/issues/1618 > >> PR: https://github.com/apache/jena/pull/1619 > >> Documentation: https://github.com/apache/jena-site/pull/131 > >> > >> * Path improvements - @SimonBin et al > >> https://github.com/apache/jena/pull/1616 > >> https://github.com/apache/jena/pull/1638 > >> Plan: https://github.com/apache/jena/issues/1629 > >> > >> * Source code folder reorganisation > >> Rename jena-tdb directory as jena-tdb1 > >> Move jena-tdb2 directory to the top level directory > >> Issue: https://github.com/apache/jena/issues/1539 > >> Issue: https://github.com/apache/jena/issues/1540 > >> > >> Contributors: > >> OyvindL Gjesdal > >> Simon Bin > >> Alexandre Ardhuin > >> Claus Stadler > >> Brian Vvosburgh > >> Eric Prud'hommeaux > >> > >> Release Vote > >> > >> Everyone, not just committers, is invited to test and vote. > >> Please download and test the proposed release. > >> > >> Staging repository: > >> > https://repository.apache.org/content/repositories/orgapachejena-1055 > >> > >> Proposed dist/ area: > >> https://dist.apache.org/repos/dist/dev/jena/ > >> > >> Keys: > >> https://svn.apache.org/repos/asf/jena/dist/KEYS > >> > >> Git commit (browser URL): > >> https://github.com/apache/jena/commit/3a62b5a5f1 > >> > >> > >> Git Commit Hash: > >> 3a62b5a5f162ef01fd46164fa11ffb5323169a61 > >> > >> Git Commit Tag: > >> jena-4.7.0 > >> > >> This vote will be open until at least > >> > >> Friday, 23rd December 2022 at 18:00 UTC > >> > >> If you expect to check the release but the time limit does not work > >> for you, please email within the schedule above. > >> > >> Thanks, > >> > >>Andy > >> > >> Checking: > >> > >> + are the GPG signatures fine? > >> + are the checksums correct? > >> + is there a source archive? > >> + can the source archive be built? > >> (NB This requires a "mvn install" first time) > >> + is there a correct LICENSE and NOTICE file in each artifact > >> (both source and binary artifacts)?
[GitHub] [jena-site] afs opened a new pull request, #133: main branch for Jena 4.7.0
afs opened a new pull request, #133: URL: https://github.com/apache/jena-site/pull/133 (trying out a process to do jena-site preparation ahead of the release) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [] Apache Jena 4.7.0 RC1
On 20/12/2022 16:44, Marco Neumann wrote: The URL to Lateral Joins is broken https://jena.apache.org/documentation/query/lateral-join.html The web site is updated when the release happens after the VOTE. It is on the "lateral-doc" branch at the moment. But go to the SPARQL CG text. Overall I think this is a good contribution but I am not happy with the name "LATERAL join" as it implies SQL LATERAL join similarities. Can we call this something else? Such as? --- It is not suddenly dropping into a release. It is mentioned in email "Towards Jena 4.7.0" It is https://github.com/apache/jena/issues/1615 And it says "This is an experimental feature." VOTE threads are first and foremost about process. --- This is a discussion for SPARQL CG: https://github.com/w3c/sparql-12/issues/100 https://github.com/w3c/sparql-12/blob/main/SEP/SEP-0006/sep-0006.md It's not what I might call a "join" (evaluate left and right arguments, then perform operation to combine the two sides) but SQL-terminolgy is often to call it a "join". https://docs.snowflake.com/en/sql-reference/constructs/join-lateral.html """ for each row in left_hand_table LHT: execute right_hand_subquery RHS using the values from the current row in the LHT """ Andy c.f. Oxigraph. Thank you, Marco . On Tue, Dec 20, 2022 at 4:39 PM Andy Seaborne wrote: Hi, Here is a vote on the release of Apache Jena 4.7.0. This is the first release candidate. The deadline is Friday, 23rd December 2022 at 18:00 UTC Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... Items in this release https://s.apache.org/jena-4.7.0-issues Major: * Lucene upgrade 8.11.1 to 9.4.1 - @OyvindLGjesdal There are changes to the stopword setting in the default configuration of Lucene's StandardAnalyzer Issue: https://github.com/apache/jena/issues/1581 PR: https://github.com/apache/jena/pull/1582 * LATERAL joins This is an experimental feature. Issue: https://github.com/apache/jena/issues/1615 Documentation: https://jena.apache.org/documentation/query/lateral-join.html * RDF Patch https://lists.apache.org/thread/8oc1gn2qnzx4ddwovx8h545jm270gpyx Issue: https://github.com/apache/jena/issues/1618 PR: https://github.com/apache/jena/pull/1619 Documentation: https://github.com/apache/jena-site/pull/131 * Path improvements - @SimonBin et al https://github.com/apache/jena/pull/1616 https://github.com/apache/jena/pull/1638 Plan: https://github.com/apache/jena/issues/1629 * Source code folder reorganisation Rename jena-tdb directory as jena-tdb1 Move jena-tdb2 directory to the top level directory Issue: https://github.com/apache/jena/issues/1539 Issue: https://github.com/apache/jena/issues/1540 Contributors: OyvindL Gjesdal Simon Bin Alexandre Ardhuin Claus Stadler Brian Vvosburgh Eric Prud'hommeaux Release Vote Everyone, not just committers, is invited to test and vote. Please download and test the proposed release. Staging repository: https://repository.apache.org/content/repositories/orgapachejena-1055 Proposed dist/ area: https://dist.apache.org/repos/dist/dev/jena/ Keys: https://svn.apache.org/repos/asf/jena/dist/KEYS Git commit (browser URL): https://github.com/apache/jena/commit/3a62b5a5f1 Git Commit Hash: 3a62b5a5f162ef01fd46164fa11ffb5323169a61 Git Commit Tag: jena-4.7.0 This vote will be open until at least Friday, 23rd December 2022 at 18:00 UTC If you expect to check the release but the time limit does not work for you, please email within the schedule above. Thanks, Andy Checking: + are the GPG signatures fine? + are the checksums correct? + is there a source archive? + can the source archive be built? (NB This requires a "mvn install" first time) + is there a correct LICENSE and NOTICE file in each artifact (both source and binary artifacts)? + does the NOTICE file contain all necessary attributions? + have any licenses of dependencies changed due to upgrades? if so have LICENSE and NOTICE been upgraded appropriately? + does the tag/commit in the SCM contain reproducible sources?
Re: [VOTE] Apache Jena 4.7.0 RC1
+1 (binding) On 20/12/2022 16:39, Andy Seaborne wrote: Hi, Here is a vote on the release of Apache Jena 4.7.0. This is the first release candidate. The deadline is Friday, 23rd December 2022 at 18:00 UTC Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... Items in this release https://s.apache.org/jena-4.7.0-issues Major: * Lucene upgrade 8.11.1 to 9.4.1 - @OyvindLGjesdal There are changes to the stopword setting in the default configuration of Lucene's StandardAnalyzer Issue: https://github.com/apache/jena/issues/1581 PR: https://github.com/apache/jena/pull/1582 * LATERAL joins This is an experimental feature. Issue: https://github.com/apache/jena/issues/1615 Documentation: https://jena.apache.org/documentation/query/lateral-join.html * RDF Patch https://lists.apache.org/thread/8oc1gn2qnzx4ddwovx8h545jm270gpyx Issue: https://github.com/apache/jena/issues/1618 PR: https://github.com/apache/jena/pull/1619 Documentation: https://github.com/apache/jena-site/pull/131 * Path improvements - @SimonBin et al https://github.com/apache/jena/pull/1616 https://github.com/apache/jena/pull/1638 Plan: https://github.com/apache/jena/issues/1629 * Source code folder reorganisation Rename jena-tdb directory as jena-tdb1 Move jena-tdb2 directory to the top level directory Issue: https://github.com/apache/jena/issues/1539 Issue: https://github.com/apache/jena/issues/1540 Contributors: OyvindL Gjesdal Simon Bin Alexandre Ardhuin Claus Stadler Brian Vvosburgh Eric Prud'hommeaux Release Vote Everyone, not just committers, is invited to test and vote. Please download and test the proposed release. Staging repository: https://repository.apache.org/content/repositories/orgapachejena-1055 Proposed dist/ area: https://dist.apache.org/repos/dist/dev/jena/ Keys: https://svn.apache.org/repos/asf/jena/dist/KEYS Git commit (browser URL): https://github.com/apache/jena/commit/3a62b5a5f1 Git Commit Hash: 3a62b5a5f162ef01fd46164fa11ffb5323169a61 Git Commit Tag: jena-4.7.0 This vote will be open until at least Friday, 23rd December 2022 at 18:00 UTC If you expect to check the release but the time limit does not work for you, please email within the schedule above. Thanks, Andy Checking: + are the GPG signatures fine? + are the checksums correct? + is there a source archive? + can the source archive be built? (NB This requires a "mvn install" first time) + is there a correct LICENSE and NOTICE file in each artifact (both source and binary artifacts)? + does the NOTICE file contain all necessary attributions? + have any licenses of dependencies changed due to upgrades? if so have LICENSE and NOTICE been upgraded appropriately? + does the tag/commit in the SCM contain reproducible sources?
Re: [VOTE] Apache Jena 4.7.0 RC1
The URL to Lateral Joins is broken https://jena.apache.org/documentation/query/lateral-join.html Overall I think this is a good contribution but I am not happy with the name "LATERAL join" as it implies SQL LATERAL join similarities. Can we call this something else? Thank you, Marco . On Tue, Dec 20, 2022 at 4:39 PM Andy Seaborne wrote: > Hi, > > Here is a vote on the release of Apache Jena 4.7.0. > This is the first release candidate. > > The deadline is > > Friday, 23rd December 2022 at 18:00 UTC > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] 0 Don't care > [ ] -1 Don't release, because ... > > Items in this release > > https://s.apache.org/jena-4.7.0-issues > > Major: > > * Lucene upgrade 8.11.1 to 9.4.1 - @OyvindLGjesdal > There are changes to the stopword setting in the default > configuration of Lucene's StandardAnalyzer >Issue: https://github.com/apache/jena/issues/1581 >PR: https://github.com/apache/jena/pull/1582 > > * LATERAL joins > This is an experimental feature. >Issue: https://github.com/apache/jena/issues/1615 >Documentation: >https://jena.apache.org/documentation/query/lateral-join.html > > * RDF Patch > https://lists.apache.org/thread/8oc1gn2qnzx4ddwovx8h545jm270gpyx >Issue: https://github.com/apache/jena/issues/1618 >PR: https://github.com/apache/jena/pull/1619 >Documentation: https://github.com/apache/jena-site/pull/131 > > * Path improvements - @SimonBin et al >https://github.com/apache/jena/pull/1616 >https://github.com/apache/jena/pull/1638 >Plan: https://github.com/apache/jena/issues/1629 > > * Source code folder reorganisation >Rename jena-tdb directory as jena-tdb1 >Move jena-tdb2 directory to the top level directory >Issue: https://github.com/apache/jena/issues/1539 >Issue: https://github.com/apache/jena/issues/1540 > > Contributors: >OyvindL Gjesdal >Simon Bin >Alexandre Ardhuin >Claus Stadler >Brian Vvosburgh >Eric Prud'hommeaux > > Release Vote > > Everyone, not just committers, is invited to test and vote. > Please download and test the proposed release. > > Staging repository: >https://repository.apache.org/content/repositories/orgapachejena-1055 > > Proposed dist/ area: >https://dist.apache.org/repos/dist/dev/jena/ > > Keys: >https://svn.apache.org/repos/asf/jena/dist/KEYS > > Git commit (browser URL): >https://github.com/apache/jena/commit/3a62b5a5f1 > > > Git Commit Hash: >3a62b5a5f162ef01fd46164fa11ffb5323169a61 > > Git Commit Tag: >jena-4.7.0 > > This vote will be open until at least > > Friday, 23rd December 2022 at 18:00 UTC > > If you expect to check the release but the time limit does not work > for you, please email within the schedule above. > > Thanks, > > Andy > > Checking: > > + are the GPG signatures fine? > + are the checksums correct? > + is there a source archive? > + can the source archive be built? >(NB This requires a "mvn install" first time) > + is there a correct LICENSE and NOTICE file in each artifact >(both source and binary artifacts)? > + does the NOTICE file contain all necessary attributions? > + have any licenses of dependencies changed due to upgrades? > if so have LICENSE and NOTICE been upgraded appropriately? > + does the tag/commit in the SCM contain reproducible sources? > -- --- Marco Neumann
[VOTE] Apache Jena 4.7.0 RC1
Hi, Here is a vote on the release of Apache Jena 4.7.0. This is the first release candidate. The deadline is Friday, 23rd December 2022 at 18:00 UTC Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... Items in this release https://s.apache.org/jena-4.7.0-issues Major: * Lucene upgrade 8.11.1 to 9.4.1 - @OyvindLGjesdal There are changes to the stopword setting in the default configuration of Lucene's StandardAnalyzer Issue: https://github.com/apache/jena/issues/1581 PR: https://github.com/apache/jena/pull/1582 * LATERAL joins This is an experimental feature. Issue: https://github.com/apache/jena/issues/1615 Documentation: https://jena.apache.org/documentation/query/lateral-join.html * RDF Patch https://lists.apache.org/thread/8oc1gn2qnzx4ddwovx8h545jm270gpyx Issue: https://github.com/apache/jena/issues/1618 PR: https://github.com/apache/jena/pull/1619 Documentation: https://github.com/apache/jena-site/pull/131 * Path improvements - @SimonBin et al https://github.com/apache/jena/pull/1616 https://github.com/apache/jena/pull/1638 Plan: https://github.com/apache/jena/issues/1629 * Source code folder reorganisation Rename jena-tdb directory as jena-tdb1 Move jena-tdb2 directory to the top level directory Issue: https://github.com/apache/jena/issues/1539 Issue: https://github.com/apache/jena/issues/1540 Contributors: OyvindL Gjesdal Simon Bin Alexandre Ardhuin Claus Stadler Brian Vvosburgh Eric Prud'hommeaux Release Vote Everyone, not just committers, is invited to test and vote. Please download and test the proposed release. Staging repository: https://repository.apache.org/content/repositories/orgapachejena-1055 Proposed dist/ area: https://dist.apache.org/repos/dist/dev/jena/ Keys: https://svn.apache.org/repos/asf/jena/dist/KEYS Git commit (browser URL): https://github.com/apache/jena/commit/3a62b5a5f1 Git Commit Hash: 3a62b5a5f162ef01fd46164fa11ffb5323169a61 Git Commit Tag: jena-4.7.0 This vote will be open until at least Friday, 23rd December 2022 at 18:00 UTC If you expect to check the release but the time limit does not work for you, please email within the schedule above. Thanks, Andy Checking: + are the GPG signatures fine? + are the checksums correct? + is there a source archive? + can the source archive be built? (NB This requires a "mvn install" first time) + is there a correct LICENSE and NOTICE file in each artifact (both source and binary artifacts)? + does the NOTICE file contain all necessary attributions? + have any licenses of dependencies changed due to upgrades? if so have LICENSE and NOTICE been upgraded appropriately? + does the tag/commit in the SCM contain reproducible sources?
