rvesse merged pull request #97:
URL: https://github.com/apache/jena-site/pull/97
--
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...@j
rvesse opened a new pull request #97:
URL: https://github.com/apache/jena-site/pull/97
Fixed some typos spotted reviewing PR #87
--
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 com
e testing.
> TDB2: read transactions sync the journal.
> -
>
> Key: JENA-2086
> URL: https://issues.apache.org/jira/browse/JENA-2086
> Project: Apache Jena
> Issue Type: Improveme
tool from 1hr to 20mins and I don't see journal synchs on VisualVM any more.
> TDB2: read transactions sync the journal.
> -
>
> Key: JENA-2086
> URL: https://issues.apache.org/jira/browse/JENA-2086
>
shot cut the running time of my rdf2pg
tool from 1hr to 20mins and I don't see journal synchs on VisualVM any more.
> TDB2: read transactions sync the journal.
> -
>
> Key: JENA-2086
> URL: https://issues.apa
revised.
> Review concurrency howto in the light of transactions.
> --
>
> Key: JENA-957
> URL: https://issues.apache.org/jira/browse/JENA-957
> Project: Apache Jena
>
I'll have time to try this week, but
should be able by the next one.
> TDB2: read transactions sync the journal.
> -
>
> Key: JENA-2086
> URL: https://issues.apache.org/jira/browse/JENA-2086
>
c in
{{TransactionCoordinator.completed}}. Read transactions do not call
{{Journal.sync}} (bonus - less sync work on write transactions).
This shouldn't now have lock pauses on completion. There is a memory-based
lock on transaction begin to get a consistent setup for a reader - that proc
[
https://issues.apache.org/jira/browse/JENA-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-2086.
-
Fix Version/s: Jena 4.1.0
Resolution: Fixed
> TDB2: read transactions sync the jour
mmit e30fecee331e7bc24a7001ab1c154bf2d298e7b3 in jena's branch
refs/heads/main from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=e30fece ]
Merge pull request #983 from afs/jena2086-txn
JENA-2086: No need to reset the journal every transaction.
> TDB2: read transacti
mmit 4e244738def9edef74084e96a4928980d1e82d93 in jena's branch
refs/heads/main from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=4e24473 ]
JENA-2086: No need to reset the journal in completed()
> TDB2: read transactions sync
pression that now it's slower from
extrapolating the previous times on the new number of triples, but it's all
quite approximate, I think the main point is it shouldn't touch the journal for
RO transactions.
was (Author: mbrandizi):
I wouldn't focus on the "why it worke
previous timings on the new number of triples, but it's all quite
approximate, I think the main point is it shouldn't touch the journal for RO
transactions.
> TDB2: read transactions sync the journal.
> -
>
> Key: JE
are completely different in
the way they work for transactions.
was (Author: andy.seaborne):
Hi Marco,
Yes, all routes go via Journal.sync. It is unnecessary for a read transaction
and I'll testing a fix that simply skips the journal in a read-cleanup. Being
this deep in the transaction
sync. It is unnecessary for a read transaction
and I'll testing a fix that simply skips the journal in a read-cleanup. Being
this deep in the transaction system, means being very careful. I haven't found
a reason while it used to work better.
> TDB2: read transactions
lso tried dataset.abort() as last step within executeRead(), but it leads
to Journal.sync() as well.
> TDB2: read transactions sync the journal.
> -
>
> Key: JENA-2086
> URL: https://issues.apache.org/jira/browse/JENA-20
[
https://issues.apache.org/jira/browse/JENA-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-2086:
Attachment: jena-sync-overhead.png
> TDB2: read transactions sync the jour
Andy Seaborne created JENA-2086:
---
Summary: TDB2: read transactions sync the journal.
Key: JENA-2086
URL: https://issues.apache.org/jira/browse/JENA-2086
Project: Apache Jena
Issue Type
[
https://issues.apache.org/jira/browse/JENA-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-1817.
-
Resolution: Fixed
> Queued writer transactions cause exception in ThreadBufferingCa
mmit 03f5253ff29ad2d011631c3d2a6c106e0230c530 in jena's branch
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=03f5253 ]
Merge pull request #672 from afs/jena1817_tdb2_node_cache
JENA-1817: Flush NodeTableCache in CommitFinish
> Queued writer transa
mmit 08ca0b8321766779978c56961d4c0820b11432d2 in jena's branch
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=08ca0b8 ]
JENA-1817: Flush NodeTableCache in CommitFinish
> Queued writer transactions cause exception in ThreadBu
Andy Seaborne created JENA-1817:
---
Summary: Queued writer transactions cause exception in
ThreadBufferingCache
Key: JENA-1817
URL: https://issues.apache.org/jira/browse/JENA-1817
Project: Apache Jena
html/ea87ca3eff5bfac3fa4c723b9bf02c0908d7146c161f9820b1b8b526@%3Cusers.jena.apache.org%3E
> Union graph does not fully handle read-transactions.
>
>
> Key: JENA-1667
> URL: https://issues.apache.o
afs merged pull request #580: JENA-1719: Work around for iterators being held
across transactions
URL: https://github.com/apache/jena/pull/580
This is an automated message from the Apache Git Service.
To respond to the
der commented on a change in pull request #580: JENA-1719: Work around for
iterators being held across transactions
URL: https://github.com/apache/jena/pull/580#discussion_r298965979
##
File path:
jena-core/src/main/java/org/apache/jena/reasoner/rulesys/impl
rvesse commented on a change in pull request #580: JENA-1719: Work around for
iterators being held across transactions
URL: https://github.com/apache/jena/pull/580#discussion_r298948482
##
File path:
jena-core/src/main/java/org/apache/jena/reasoner/rulesys/impl
rvesse commented on a change in pull request #580: JENA-1719: Work around for
iterators being held across transactions
URL: https://github.com/apache/jena/pull/580#discussion_r298946940
##
File path:
jena-core/src/main/java/org/apache/jena/reasoner/rulesys/impl
der opened a new pull request #580: JENA-1719: Work around for iterators being
held across transactions
URL: https://github.com/apache/jena/pull/580
Provides a workaround to #JENA-1719.
Underlying problem is that when inferences are not run to completion
then tabled goals and
Andy Seaborne created JENA-1667:
---
Summary: Union graph does not fully handle read-transactions.
Key: JENA-1667
URL: https://issues.apache.org/jira/browse/JENA-1667
Project: Apache Jena
Issue
[
https://issues.apache.org/jira/browse/JENA-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-1631.
-
Resolution: Fixed
Fix Version/s: Jena 3.10.0
> "update" command line tool
mmit ea7c22d7bdf523384a2fd134a610130299db409d in jena's branch
refs/heads/master from [~an...@apache.org]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=ea7c22d ]
JENA-1631: Use DatasetGraphMapLink transactions.
> "update" command
[
https://issues.apache.org/jira/browse/JENA-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne reassigned JENA-1631:
---
Assignee: Andy Seaborne
> "update" command line tool
[
https://issues.apache.org/jira/browse/JENA-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-1631:
Labels: (was: features usability)
> "update" command line tool
[
https://issues.apache.org/jira/browse/JENA-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16685768#comment-16685768
]
Andy Seaborne commented on JENA-1631:
-
{{jena.update}} does support transactions
[
https://issues.apache.org/jira/browse/JENA-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-1631:
Priority: Major (was: Blocker)
> "update" command line tool
Laura created JENA-1631:
---
Summary: "update" command line tool transactions
Key: JENA-1631
URL: https://issues.apache.org/jira/browse/JENA-1631
Project: Apache Jena
Issue Type: I
[
https://issues.apache.org/jira/browse/JENA-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A. Soroka resolved JENA-1605.
-
Resolution: Fixed
> spatialindexer doesn't use tran
mmit 4816dcecd2992a8236ebbebb30ad2a1796aab92c in jena's branch
refs/heads/master from ajs6f
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=4816dce ]
JENA-1605: use transactions in spatialindexer
> spatialindexer doesn't
uest at:
https://github.com/apache/jena/pull/471
> spatialindexer doesn't use transactions
> ---
>
> Key: JENA-1605
> URL: https://issues.apache.org/jira/browse/JENA-1605
> Project: Apache
Github user asfgit closed the pull request at:
https://github.com/apache/jena/pull/471
---
uest:
https://github.com/apache/jena/pull/471
JENA-1605: use transactions in spatialindexer
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ajs6f/jena JENA-1605
Alternatively you can review and apply these changes as the patc
GitHub user ajs6f opened a pull request:
https://github.com/apache/jena/pull/471
JENA-1605: use transactions in spatialindexer
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ajs6f/jena JENA-1605
Alternatively you can review
A. Soroka created JENA-1605:
---
Summary: spatialindexer doesn't use transactions
Key: JENA-1605
URL: https://issues.apache.org/jira/browse/JENA-1605
Project: Apache Jena
Issue Type
oss transactions.
> ---
>
> Key: JENA-1527
> URL: https://issues.apache.org/jira/browse/JENA-1527
> Project: Apache Jena
> Issue Type: Bug
> Components: TDB
>A
mmit ec67a007074b6beb42c72ae9a257e1876dd4a8b1 in jena's branch
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=ec67a00 ]
JENA-1527: Create PrefixMap on each getPrefixMapping
> GraphTDB caches prefix map across
t at:
https://github.com/apache/jena/pull/402
> GraphTDB caches prefix map across transactions.
> ---
>
> Key: JENA-1527
> URL: https://issues.apache.org/jira/browse/JENA-1527
>
ches prefix map across transactions.
> ---
>
> Key: JENA-1527
> URL: https://issues.apache.org/jira/browse/JENA-1527
> Project: Apache Jena
> Issue Type: Bug
> Compon
[
https://issues.apache.org/jira/browse/JENA-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-1527:
Summary: GraphTDB caches prefix map across transactions. (was: GraphDB
caches prefix map across
1:14:09Z
JENA-1527: Create PrefixMap on each getPrefixMapping
> GraphDB caches prefix map across transactions.
> --
>
> Key: JENA-1527
> URL: https://issues.apache.org/jira/browse/JENA-1527
&g
Andy Seaborne created JENA-1527:
---
Summary: GraphDB caches prefix map across transactions.
Key: JENA-1527
URL: https://issues.apache.org/jira/browse/JENA-1527
Project: Apache Jena
Issue Type
[
https://issues.apache.org/jira/browse/JENA-530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne closed JENA-530.
--
Resolution: Duplicate
Fix Version/s: Jena 3.7.0
> Transactions (model and dataset) need
t at:
https://github.com/apache/jena/pull/369
> Transactions not passed down for nested models.
> ---
>
> Key: JENA-1492
> URL: https://issues.apache.org/jira/browse/JENA-1492
>
[
https://issues.apache.org/jira/browse/JENA-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-1492.
-
Resolution: Fixed
Assignee: Andy Seaborne
Fix Version/s: Jena 3.7.0
> Transacti
Github user asfgit closed the pull request at:
https://github.com/apache/jena/pull/369
---
che.jena.shared.LockMRSW;
+import org.apache.jena.sparql.JenaTransactionException;
+
+/**
+ * A {@link Transactional} that passes the transaction operations down to
transactions on
+ * independent graphs.
+ *
+ * There are limitations:
+ *
+ * we can't atomically d
na.reasoner.InfGraph;
+import org.apache.jena.shared.LockMRSW;
+import org.apache.jena.sparql.JenaTransactionException;
+
+/**
+ * A {@link Transactional} that passes the transaction operations down to
transactions on
+ * independent graphs.
+ *
+ * There are limitations:
ed.LockMRSW;
+import org.apache.jena.sparql.JenaTransactionException;
+
+/**
+ * A {@link Transactional} that passes the transaction operations down to
transactions on
+ * independent graphs.
+ *
+ * There are limitations:
+ *
+ * we can't atomically do al
na.reasoner.InfGraph;
+import org.apache.jena.shared.LockMRSW;
+import org.apache.jena.sparql.JenaTransactionException;
+
+/**
+ * A {@link Transactional} that passes the transaction operations down to
transactions on
+ * independent graphs.
+ *
+ * There are limitations:
+
che.jena.shared.LockMRSW;
+import org.apache.jena.sparql.JenaTransactionException;
+
+/**
+ * A {@link Transactional} that passes the transaction operations down to
transactions on
+ * independent graphs.
+ *
+ * There are limitations:
+ *
+ * we can't atomically d
na.reasoner.InfGraph;
+import org.apache.jena.shared.LockMRSW;
+import org.apache.jena.sparql.JenaTransactionException;
+
+/**
+ * A {@link Transactional} that passes the transaction operations down to
transactions on
+ * independent graphs.
+ *
+ * There are limitations:
ed.LockMRSW;
+import org.apache.jena.sparql.JenaTransactionException;
+
+/**
+ * A {@link Transactional} that passes the transaction operations down to
transactions on
+ * independent graphs.
+ *
+ * There are limitations:
+ *
+ * we can't atomically do al
na.reasoner.InfGraph;
+import org.apache.jena.shared.LockMRSW;
+import org.apache.jena.sparql.JenaTransactionException;
+
+/**
+ * A {@link Transactional} that passes the transaction operations down to
transactions on
+ * independent graphs.
+ *
+ * There are limitations:
+
che.jena.shared.LockMRSW;
+import org.apache.jena.sparql.JenaTransactionException;
+
+/**
+ * A {@link Transactional} that passes the transaction operations down to
transactions on
+ * independent graphs.
+ *
+ * There are limitations:
+ *
+ * we can't atomically d
na.reasoner.InfGraph;
+import org.apache.jena.shared.LockMRSW;
+import org.apache.jena.sparql.JenaTransactionException;
+
+/**
+ * A {@link Transactional} that passes the transaction operations down to
transactions on
+ * independent graphs.
+ *
+ * There are limitations:
na.reasoner.InfGraph;
+import org.apache.jena.shared.LockMRSW;
+import org.apache.jena.sparql.JenaTransactionException;
+
+/**
+ * A {@link Transactional} that passes the transaction operations down to
transactions on
+ * independent graphs.
+ *
+ * There are limitations:
che.jena.shared.LockMRSW;
+import org.apache.jena.sparql.JenaTransactionException;
+
+/**
+ * A {@link Transactional} that passes the transaction operations down to
transactions on
+ * independent graphs.
+ *
+ * There are limitations:
+ *
+ * we can't atomically d
che.jena.shared.LockMRSW;
+import org.apache.jena.sparql.JenaTransactionException;
+
+/**
+ * A {@link Transactional} that passes the transaction operations down to
transactions on
+ * independent graphs.
+ *
+ * There are limitations:
+ *
+ * we can't atomically d
che.jena.shared.LockMRSW;
+import org.apache.jena.sparql.JenaTransactionException;
+
+/**
+ * A {@link Transactional} that passes the transaction operations down to
transactions on
+ * independent graphs.
+ *
+ * There are limitations:
+ *
+ * we can't atomically d
na.reasoner.InfGraph;
+import org.apache.jena.shared.LockMRSW;
+import org.apache.jena.sparql.JenaTransactionException;
+
+/**
+ * A {@link Transactional} that passes the transaction operations down to
transactions on
+ * independent graphs.
+ *
+ * There are limitations:
na.reasoner.InfGraph;
+import org.apache.jena.shared.LockMRSW;
+import org.apache.jena.sparql.JenaTransactionException;
+
+/**
+ * A {@link Transactional} that passes the transaction operations down to
transactions on
+ * independent graphs.
+ *
+ * There are limitations:
iles#diff-9d27f4f9095b5d190b6fe8977b6c393b).
From what I understand, this all makes sense. Datasets that are "collected"
from multiple graphs can, at best, pass the transaction through to their
graphs, those that are in control of their own data can retain the
responsibili
che.jena.shared.LockMRSW;
+import org.apache.jena.sparql.JenaTransactionException;
+
+/**
+ * A {@link Transactional} that passes the transaction operations down to
transactions on
+ * independent graphs.
+ *
+ * There are limitations:
+ *
+ * we can't atomically d
na.reasoner.InfGraph;
+import org.apache.jena.shared.LockMRSW;
+import org.apache.jena.sparql.JenaTransactionException;
+
+/**
+ * A {@link Transactional} that passes the transaction operations down to
transactions on
+ * independent graphs.
+ *
+ * There are limitations:
ir own data can retain the
responsibility for transactions themselves. That does seem to be the least
surprising behavior and the one that veers towards "dataset as the fundamental
unit" which we have been working towards.
---
ssue:
https://github.com/apache/jena/pull/369
Yes, this is models passing down transactions. It only became possible
with dataset-transaction promotion (new to 3.7.0).
This all has a lot of knock on consequences. The wrap/create distinction is
quite important and that touches a lo
Github user afs commented on the issue:
https://github.com/apache/jena/pull/369
Yes, this is models passing down transactions. It only became possible
with dataset-transaction promotion (new to 3.7.0).
This all has a lot of knock on consequences. The wrap/create
r wrapped models (which should pass them into their underlying
`Dataset`)?
> Transactions not passed down for nested models.
> ---
>
> Key: JENA-1492
> URL: https://issues.apache.org/jira/browse/JENA-14
Github user ajs6f commented on the issue:
https://github.com/apache/jena/pull/369
There is some new `Assembler` stuff and reformatting, so I'm not totally
clear what the thrust of this PR is: is it to ensure that `Model`s wrapping
other `Model`s (e.g. for inferencing) correctly pass t
ssue:
https://github.com/apache/jena/pull/369
"Skolemization function" is not related; it is a small clarification done
in passing.
> Transactions not passed down for nested models.
> ---
>
> Key: JENA-1492
&g
uest:
https://github.com/apache/jena/pull/369
JENA-1492: Pass down transactions from general datasets
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/afs/jena txn-general
Alternatively you can review and apply these changes as the patc
GitHub user afs opened a pull request:
https://github.com/apache/jena/pull/369
JENA-1492: Pass down transactions from general datasets
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/afs/jena txn-general
Alternatively you can
Github user afs commented on the issue:
https://github.com/apache/jena/pull/369
"Skolemization function" is not related; it is a small clarification done
in passing.
---
[
https://issues.apache.org/jira/browse/JENA-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16369943#comment-16369943
]
A. Soroka commented on JENA-1492:
-
This means transactions initiated on the "
tdb2:dataset :datasetTDB2 .
## TDB2 database
:datasetTDB2 rdf:type tdb2:DatasetTDB2 ;
tdb2:location "DB2".
{noformat}
> Transactions not passed down for nested models.
> ---
>
> Key: JENA-1492
>
[
https://issues.apache.org/jira/browse/JENA-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-1492:
Attachment: config-tdb2-model.ttl
> Transactions not passed down for nested mod
Andy Seaborne created JENA-1492:
---
Summary: Transactions not passed down for nested models.
Key: JENA-1492
URL: https://issues.apache.org/jira/browse/JENA-1492
Project: Apache Jena
Issue Type
Github user asfgit closed the pull request at:
https://github.com/apache/jena/pull/359
---
Github user ajs6f commented on the issue:
https://github.com/apache/jena/pull/359
I meant code review. (I have no problem believing that I overlooked them,
just surprised that everyone did.)
---
Github user afs commented on the issue:
https://github.com/apache/jena/pull/359
Not in the 3.6.0 release.
---
GitHub user afs opened a pull request:
https://github.com/apache/jena/pull/359
Fixes for transactions after JENA-1458
Always check autogenerated code!
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/afs/jena ds-impl-fixes
ort transactions
> -
>
> Key: JENA-1457
> URL: https://issues.apache.org/jira/browse/JENA-1457
> Project: Apache Jena
> Issue Type: Bug
> Components: Core
>
t at:
https://github.com/apache/jena/pull/352
> Graph contract tests do not properly support transactions
> -
>
> Key: JENA-1457
> URL: https://issues.apache.org/jira/browse/JENA-1457
&g
mmit 8567e272d8d1bb33284ee2c4bdba056b69d76139 in jena's branch
refs/heads/master from [~cla...@xenei.org]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=8567e27 ]
JENA-1457 Fix graph contract test transaction usage
this closes #352
> Graph contract tests do not properly support
04T11:05:28Z
Merge branch 'master' into FixGraphContractTestTransactionUsage
commit 0d0beae44bf92ddb7b4b755d58819621d7163d75
Author: Claude Warren
Date: 2018-02-04T11:11:46Z
reverted to master version
> Graph contract tests do not properly support transactions
> ---
uest at:
https://github.com/apache/jena/pull/343
> Graph contract tests do not properly support transactions
> -
>
> Key: JENA-1457
> URL: https://issues.apache.org/jira/browse/JENA-1457
&g
)) );
```
makes the tests shorter and clearer.
> Graph contract tests do not properly support transactions
> -
>
> Key: JENA-1457
> URL: https://issues.apache.org/jira/browse/JE
ssue:
https://github.com/apache/jena/pull/343
Yes - there are problems with JSONInput. This is visible in the {{.patch}}
form. It looks like changes were copied from Jena master and separately
committed.
> Graph contract tests do not properly support trans
hor: Claude Warren
Date: 2018-01-21T13:12:19Z
fixes JENA-1457
Removed incorrect JSONInput.java
> Graph contract tests do not properly support transactions
> -
>
> Key: JENA-1457
>
[
https://issues.apache.org/jira/browse/JENA-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Warren reassigned JENA-1457:
---
Assignee: Claude Warren
> Graph contract tests do not properly support transacti
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 wel
1 - 100 of 216 matches
Mail list logo
