[jira] [Commented] (JENA-1815) Join strategy/VarFinder: deal with assigned variables (AS) differently to pattern defined variables.
[
https://issues.apache.org/jira/browse/JENA-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17087075#comment-17087075
]
Andy Seaborne commented on JENA-1815:
-
Some related tickets:
JENA-1121
JENA-1257
JENA-1018
JENA-1028
JENA-1187
> Join strategy/VarFinder: deal with assigned variables (AS) differently to
> pattern defined variables.
>
>
> Key: JENA-1815
> URL: https://issues.apache.org/jira/browse/JENA-1815
> Project: Apache Jena
> Issue Type: Improvement
>Affects Versions: Jena 3.13.1, Jena 3.14.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
>
> The {{VarFinder}} treats assigned variables ({{AS ?var}}) in the same way as
> variables set by pattern. In the sense that these two forms both set
> variables, this is correct but "AS variables" can not be substituted for. At
> the moment join classification says that a join is not "linear" (i.e.
> {{sequence}} can be used) when assignment is encountered.
> By classifying variables into substituable and non-substitutable, it should
> be possible to do a better job of optimization choices of the join strategy.
> This is motivated by JENA-1813.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (JENA-1815) Join strategy/VarFinder: deal with assigned variables (AS) differently to pattern defined variables.
[
https://issues.apache.org/jira/browse/JENA-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17045393#comment-17045393
]
Andy Seaborne commented on JENA-1815:
-
I haven't seen a PR come in so I can't say what might happen.
Did the workaround for TopQuadrant work?
BTW The next release is 3.15.0.
> Join strategy/VarFinder: deal with assigned variables (AS) differently to
> pattern defined variables.
>
>
> Key: JENA-1815
> URL: https://issues.apache.org/jira/browse/JENA-1815
> Project: Apache Jena
> Issue Type: Improvement
>Affects Versions: Jena 3.13.1, Jena 3.14.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
>
> The {{VarFinder}} treats assigned variables ({{AS ?var}}) in the same way as
> variables set by pattern. In the sense that these two forms both set
> variables, this is correct but "AS variables" can not be substituted for. At
> the moment join classification says that a join is not "linear" (i.e.
> {{sequence}} can be used) when assignment is encountered.
> By classifying variables into substituable and non-substitutable, it should
> be possible to do a better job of optimization choices of the join strategy.
> This is motivated by JENA-1813.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (JENA-1815) Join strategy/VarFinder: deal with assigned variables (AS) differently to pattern defined variables.
[
https://issues.apache.org/jira/browse/JENA-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17045006#comment-17045006
]
Ken Treimann commented on JENA-1815:
Could this possibly be added to 3.14.1?
> Join strategy/VarFinder: deal with assigned variables (AS) differently to
> pattern defined variables.
>
>
> Key: JENA-1815
> URL: https://issues.apache.org/jira/browse/JENA-1815
> Project: Apache Jena
> Issue Type: Improvement
>Affects Versions: Jena 3.13.1, Jena 3.14.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
>
> The {{VarFinder}} treats assigned variables ({{AS ?var}}) in the same way as
> variables set by pattern. In the sense that these two forms both set
> variables, this is correct but "AS variables" can not be substituted for. At
> the moment join classification says that a join is not "linear" (i.e.
> {{sequence}} can be used) when assignment is encountered.
> By classifying variables into substituable and non-substitutable, it should
> be possible to do a better job of optimization choices of the join strategy.
> This is motivated by JENA-1813.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
