[jira] [Commented] (JENA-1457) Graph contract tests do not properly support transactions
[ https://issues.apache.org/jira/browse/JENA-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16307263#comment-16307263 ] A. Soroka commented on JENA-1457: - Just to be extra-clear: TIM doesn't require explicit transactions, but any non-transactional calls on it get auto-wrapped per call into single-call-payload transactions. Expensive and slow! So one can mix explicit and non-explicit transactional behavior against TIM (there really is no non-transactional behavior for TIM), but users are well-advised to be as explicit as possible. So it seems like TIM or TDB2 graphs are always transactional and other dataset impls, not so much, but I don't know that we can represent very well that at this point in the API/contracts. It seems like that boat has sailed on the same tide that sent immutable graphs out to sea. Maybe we can think about representing transactionality differently in a new API? > Graph contract tests do not properly support transactions > - > > Key: JENA-1457 > URL: https://issues.apache.org/jira/browse/JENA-1457 > Project: Apache Jena > Issue Type: Bug > Components: Core >Reporter: Claude Warren >Priority: Minor > > The Contract test for Graphs do not properly support transactions. > Specifically, if the graph supports transactions all actions should be > enclosed within a transaction. > The easiest test for this is to test the GraphTxnTDB implementation as it > will fail if transactions are not properly used. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (JENA-1457) Graph contract tests do not properly support transactions
[ https://issues.apache.org/jira/browse/JENA-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16307222#comment-16307222 ] Andy Seaborne commented on JENA-1457: - Some graphs support transactional and non-transactional behaviour. The contract tests have no way to be configured. At the moment, TDB2 requires explicit transactions and it's the only one of the project's storage components that does. TIM and TDB1 do not require transactions, though once a TDB1 dataset has been used transactionally, it must always be used transactionally. This does not apply to TIM. As we have seen on dev@, some tests are not about the graph contract. If two graphs are involved, the contract says nothing about their interacting behaviour, and shouldn't because the choices are part of why one storage component is chosen over another . (Graph capabilities can not capture this as it is a closed up-front set of options. > Graph contract tests do not properly support transactions > - > > Key: JENA-1457 > URL: https://issues.apache.org/jira/browse/JENA-1457 > Project: Apache Jena > Issue Type: Bug > Components: Core >Reporter: Claude Warren >Priority: Minor > > The Contract test for Graphs do not properly support transactions. > Specifically, if the graph supports transactions all actions should be > enclosed within a transaction. > The easiest test for this is to test the GraphTxnTDB implementation as it > will fail if transactions are not properly used. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (JENA-1454) Configurable ResultSet reading and writing
[
https://issues.apache.org/jira/browse/JENA-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16307180#comment-16307180
]
ASF subversion and git services commented on JENA-1454:
---
Commit 1ea47368f593c17092645e120f6949f63c178e8c in jena's branch
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=1ea4736 ]
JENA-1454: Tests for bnode handling
> Configurable ResultSet reading and writing
> --
>
> Key: JENA-1454
> URL: https://issues.apache.org/jira/browse/JENA-1454
> Project: Apache Jena
> Issue Type: Improvement
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.7.0
>
>
> Same patterns as {{RDFParser}}, {{RDFWriter}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (JENA-1454) Configurable ResultSet reading and writing
[
https://issues.apache.org/jira/browse/JENA-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16307183#comment-16307183
]
ASF subversion and git services commented on JENA-1454:
---
Commit 0366da2c37b64978893897eba068fdb6b47ea782 in jena's branch
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=0366da2 ]
JENA-1454: Merge commit 'refs/pull/334/head' of github.com:apache/jena
This closes #334.
> Configurable ResultSet reading and writing
> --
>
> Key: JENA-1454
> URL: https://issues.apache.org/jira/browse/JENA-1454
> Project: Apache Jena
> Issue Type: Improvement
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.7.0
>
>
> Same patterns as {{RDFParser}}, {{RDFWriter}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[GitHub] jena pull request #334: JENA-1454: Introduce builder pattern for result set ...
Github user asfgit closed the pull request at: https://github.com/apache/jena/pull/334 ---
[jira] [Commented] (JENA-1454) Configurable ResultSet reading and writing
[
https://issues.apache.org/jira/browse/JENA-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16307181#comment-16307181
]
ASF subversion and git services commented on JENA-1454:
---
Commit b022dc1ed532386b03bf5bb2669ee469f367411b in jena's branch
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=b022dc1 ]
JENA-1454: Checks of arguments
> Configurable ResultSet reading and writing
> --
>
> Key: JENA-1454
> URL: https://issues.apache.org/jira/browse/JENA-1454
> Project: Apache Jena
> Issue Type: Improvement
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.7.0
>
>
> Same patterns as {{RDFParser}}, {{RDFWriter}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (JENA-1454) Configurable ResultSet reading and writing
[
https://issues.apache.org/jira/browse/JENA-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16307182#comment-16307182
]
ASF subversion and git services commented on JENA-1454:
---
Commit 1e1da9570e2d07a1500d85c2b2b1e495624ece00 in jena's branch
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=1e1da95 ]
JENA-1454: Use of new result set machinery for HTTP responses
> Configurable ResultSet reading and writing
> --
>
> Key: JENA-1454
> URL: https://issues.apache.org/jira/browse/JENA-1454
> Project: Apache Jena
> Issue Type: Improvement
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.7.0
>
>
> Same patterns as {{RDFParser}}, {{RDFWriter}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (JENA-1454) Configurable ResultSet reading and writing
[
https://issues.apache.org/jira/browse/JENA-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-1454.
-
Resolution: Fixed
Fix Version/s: Jena 3.7.0
> Configurable ResultSet reading and writing
> --
>
> Key: JENA-1454
> URL: https://issues.apache.org/jira/browse/JENA-1454
> Project: Apache Jena
> Issue Type: Improvement
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.7.0
>
>
> Same patterns as {{RDFParser}}, {{RDFWriter}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
