[jira] [Updated] (JENA-1078) TxnMem does not log a warning when commit() omitted.
[
https://issues.apache.org/jira/browse/JENA-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-1078:
Description:
Example:
{noformat}
Dataset ds = DatasetFactory.createTxnMem() ;
//Dataset ds = TDBFactory.createDataset() ;
ds.begin(ReadWrite.WRITE) ;
//ds.commit();
ds.end() ;
{noformat}
whereas a read transaction can be:
{noformat}
Dataset ds = DatasetFactory.createTxnMem() ;
ds.begin(ReadWrite.READ) ;
ds.end() ;
{noformat}
See javadoc for {{org.apache.jena.sparql.core.Transactional}}
was:
Example:
{noformat}
Dataset ds = DatasetFactory.createTxnMem() ;
//Dataset ds = TDBFactory.createDataset() ;
ds.begin(ReadWrite.WRITE) ;
//ds.commit();
ds.end() ;
{noformat}
> TxnMem does not log a warning when commit() omitted.
>
>
> Key: JENA-1078
> URL: https://issues.apache.org/jira/browse/JENA-1078
> Project: Apache Jena
> Issue Type: Bug
>Affects Versions: Jena 3.0.1
>Reporter: Andy Seaborne
> Fix For: Jena 3.1.0
>
>
> Example:
> {noformat}
> Dataset ds = DatasetFactory.createTxnMem() ;
> //Dataset ds = TDBFactory.createDataset() ;
> ds.begin(ReadWrite.WRITE) ;
> //ds.commit();
> ds.end() ;
> {noformat}
> whereas a read transaction can be:
> {noformat}
> Dataset ds = DatasetFactory.createTxnMem() ;
> ds.begin(ReadWrite.READ) ;
> ds.end() ;
> {noformat}
> See javadoc for {{org.apache.jena.sparql.core.Transactional}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: [jira] [Resolved] (JENA-955) Review security documentation
On 08/12/15 21:06, Claude Warren (JIRA) wrote: [ https://issues.apache.org/jira/browse/JENA-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claude Warren resolved JENA-955. Resolution: Fixed Fix Version/s: Jena 3.0.0 Security was renamed Permissions. All documentation appears to be in place for permissions. I checked the javadoc index page and it was wrong. It is corrected in the staging jena 3.0.1 website. Andy Please mark unresolved if there are any issues. Review security documentation - Key: JENA-955 URL: https://issues.apache.org/jira/browse/JENA-955 Project: Apache Jena Issue Type: Documentation Components: Security Reporter: Bruno P. Kinoshita Assignee: Claude Warren Priority: Trivial Labels: documentation Fix For: Jena 3.0.0 Review the current documentation for the security module, and check if there's any enhancements, or if anything changed after the Jena3 branch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: A release?
I put some documentation in at
http://jena.staging.apache.org/documentation/rdf/datasets.html
because the announcement needs to link to something. I hope I got it
right. This can be changed between releases -- the bytes aren't in the
release itself.
(The file name was chosen so that more general text could go there and
this becomes a section of documentation about dataset usage in Jena)
Andy
On 08/12/15 14:53, A. Soroka wrote:
That should certainly “enlist” a number of RC testers. {grin}
I will stand by for bug fixes.
---
A. Soroka
The University of Virginia Library
On Dec 8, 2015, at 3:38 AM, Andy Seaborne wrote:
On 23/11/15 15:31, A. Soroka wrote:
A weightless +1 from me, of course! {grin} I’m excited to see this stuff get in
front of people.
I’m not sure what you mean by “Fuseki integration”, Andy. Do you mean to make
the new dataset impl available as an option in Fuseki (presumably in both the
web admin UI and the CLI for the standalone server)?
Fuseki should chnage to using the new in-memory txn dataset when creating new
in-memory setups. So the template-driven assemblers (UI) and from the command
line (--mem) will change. Existing setups are preserved because the template
is used to create an assembler when first used, not each start-up.
Andy
---
A. Soroka
The University of Virginia Library
On Nov 23, 2015, at 10:24 AM, Andy Seaborne wrote:
We have:
* in-memory transactional dataset from Adam is in the codebase
(details on progress below)
* configurable lucene analyzers
* general maintenance.
* Improved start-up and configuration to wire the jars together.
Shall we do a release? This fits our 3-6 months cycle.
As we know, getting people to try unreleased builds has limited effect (generally for
point-bug fixes, less so for new features) so my suggestion is to release soon as v3.0.1
and describe the in-memory transactional dataset as "RC". It's not fully
integrated (test: Fuseki is not using it yet) and getting that done and stable isn't an
instant task to do. At the same time, a release will let people try it.
So we expose the in-memory transactional dataset at the API level now,
introduce the deprecations so people can see what's coming, and
complete/stabilize the integration to make a v3.1.0 in a few months time.
Andy
Progress on the in-memory transactional dataset
https://pony-poc.apache.org/thread.html/Zj36f2pbaszgdnj
If you want to try it, then DatasetFactory.createTxnMem() is the entry point.
Outstanding tasks:
* Dependency version management in jena-parent.
Done
* more testing [done], and the organisation of the tests
Test done, organisation of tests is partially done. There is a wider tasks to
organise the dataset tests we have into some sort of order but that's
non-blocking.
* documentation
* code cleaning for deprecation of DatasetFactory.createMem
* Same migration for DatasetGraphFactory.createMem
* Fuseki integration
Re: [VOTE] Release Jena 3.0.1 and Fuseki 2.3.1
+1 To build, it is necessary to "mvn install" because of the shaded Guava -- simply "mvn test" would work from the compiled class files of other modules which is not how shading works. Andy Dependency changes: Added: com.github.andrewoma.dexx::dexx-collections:0.2 (for testing) com.jayway.awaitility:awaitility:1.6.4 Updates: jsonld-java : 0.5.1 -> 0.7.0 httpcore 4.2.5 -> 4.2.6 Everyone, not just committers, is invited to test and vote. Staging repository: https://repository.apache.org/content/repositories/orgapachejena-1010/ 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): http://git-wip-us.apache.org/repos/asf/jena/commit/499317ad Git Commit Hash: 499317adff7902195ae4fa87254d6c176b6fb1d6 Git Commit Tag: jena-3.0.1-rc1 Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This vote will be open to at least the end of Friday, 11th December 2015, 23:59 UTC
[jira] [Commented] (JENA-1078) TxnMem does not log a warning when commit() omitted.
[
https://issues.apache.org/jira/browse/JENA-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15048516#comment-15048516
]
ASF GitHub Bot commented on JENA-1078:
--
Github user afs commented on a diff in the pull request:
https://github.com/apache/jena/pull/105#discussion_r47078789
--- Diff:
jena-arq/src/main/java/org/apache/jena/sparql/core/mem/DatasetGraphInMemory.java
---
@@ -161,17 +161,17 @@ public void abort() {
@Override
public void close() {
if (isInTransaction()) abort();
-
}
@Override
public void end() {
if (isInTransaction()) {
+log.warn("Ending transaction without commit!");
--- End diff --
begin(READ)-end() is a normal pattern. The code needs to know if it is
considering a READ or WRITE transaction.
> TxnMem does not log a warning when commit() omitted.
>
>
> Key: JENA-1078
> URL: https://issues.apache.org/jira/browse/JENA-1078
> Project: Apache Jena
> Issue Type: Bug
>Affects Versions: Jena 3.0.1
>Reporter: Andy Seaborne
> Fix For: Jena 3.1.0
>
>
> Example:
> {noformat}
> Dataset ds = DatasetFactory.createTxnMem() ;
> //Dataset ds = TDBFactory.createDataset() ;
> ds.begin(ReadWrite.WRITE) ;
> //ds.commit();
> ds.end() ;
> {noformat}
> whereas a read transaction can be:
> {noformat}
> Dataset ds = DatasetFactory.createTxnMem() ;
> ds.begin(ReadWrite.READ) ;
> ds.end() ;
> {noformat}
> See javadoc for {{org.apache.jena.sparql.core.Transactional}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] jena pull request: JENA-1078: Logging warning when transaction is ...
Github user afs commented on a diff in the pull request:
https://github.com/apache/jena/pull/105#discussion_r47078789
--- Diff:
jena-arq/src/main/java/org/apache/jena/sparql/core/mem/DatasetGraphInMemory.java
---
@@ -161,17 +161,17 @@ public void abort() {
@Override
public void close() {
if (isInTransaction()) abort();
-
}
@Override
public void end() {
if (isInTransaction()) {
+log.warn("Ending transaction without commit!");
--- End diff --
begin(READ)-end() is a normal pattern. The code needs to know if it is
considering a READ or WRITE transaction.
---
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: JENA-1078: Logging warning when transaction is ...
Github user ajs6f commented on a diff in the pull request:
https://github.com/apache/jena/pull/105#discussion_r47086225
--- Diff:
jena-arq/src/main/java/org/apache/jena/sparql/core/mem/DatasetGraphInMemory.java
---
@@ -161,17 +161,17 @@ public void abort() {
@Override
public void close() {
if (isInTransaction()) abort();
-
}
@Override
public void end() {
if (isInTransaction()) {
+log.warn("Ending transaction without commit!");
--- End diff --
Fixed with latest commit.
---
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] [Commented] (JENA-1078) TxnMem does not log a warning when commit() omitted.
[
https://issues.apache.org/jira/browse/JENA-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15048628#comment-15048628
]
ASF GitHub Bot commented on JENA-1078:
--
Github user ajs6f commented on a diff in the pull request:
https://github.com/apache/jena/pull/105#discussion_r47086225
--- Diff:
jena-arq/src/main/java/org/apache/jena/sparql/core/mem/DatasetGraphInMemory.java
---
@@ -161,17 +161,17 @@ public void abort() {
@Override
public void close() {
if (isInTransaction()) abort();
-
}
@Override
public void end() {
if (isInTransaction()) {
+log.warn("Ending transaction without commit!");
--- End diff --
Fixed with latest commit.
> TxnMem does not log a warning when commit() omitted.
>
>
> Key: JENA-1078
> URL: https://issues.apache.org/jira/browse/JENA-1078
> Project: Apache Jena
> Issue Type: Bug
>Affects Versions: Jena 3.0.1
>Reporter: Andy Seaborne
> Fix For: Jena 3.1.0
>
>
> Example:
> {noformat}
> Dataset ds = DatasetFactory.createTxnMem() ;
> //Dataset ds = TDBFactory.createDataset() ;
> ds.begin(ReadWrite.WRITE) ;
> //ds.commit();
> ds.end() ;
> {noformat}
> whereas a read transaction can be:
> {noformat}
> Dataset ds = DatasetFactory.createTxnMem() ;
> ds.begin(ReadWrite.READ) ;
> ds.end() ;
> {noformat}
> See javadoc for {{org.apache.jena.sparql.core.Transactional}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: A release?
Is it possible for non-committers to see that? I get a login dialog with the
message "ASF Committers”.
---
A. Soroka
The University of Virginia Library
> On Dec 9, 2015, at 5:20 AM, Andy Seaborne wrote:
>
> I put some documentation in at
>
> http://jena.staging.apache.org/documentation/rdf/datasets.html
>
> because the announcement needs to link to something. I hope I got it right.
> This can be changed between releases -- the bytes aren't in the release
> itself.
>
> (The file name was chosen so that more general text could go there and this
> becomes a section of documentation about dataset usage in Jena)
>
> Andy
>
> On 08/12/15 14:53, A. Soroka wrote:
>> That should certainly “enlist” a number of RC testers. {grin}
>>
>> I will stand by for bug fixes.
>>
>> ---
>> A. Soroka
>> The University of Virginia Library
>>
>>> On Dec 8, 2015, at 3:38 AM, Andy Seaborne wrote:
>>>
>>> On 23/11/15 15:31, A. Soroka wrote:
A weightless +1 from me, of course! {grin} I’m excited to see this stuff
get in front of people.
I’m not sure what you mean by “Fuseki integration”, Andy. Do you mean to
make the new dataset impl available as an option in Fuseki (presumably in
both the web admin UI and the CLI for the standalone server)?
>>>
>>> Fuseki should chnage to using the new in-memory txn dataset when creating
>>> new in-memory setups. So the template-driven assemblers (UI) and from the
>>> command line (--mem) will change. Existing setups are preserved because
>>> the template is used to create an assembler when first used, not each
>>> start-up.
>>>
>>> Andy
>>>
---
A. Soroka
The University of Virginia Library
> On Nov 23, 2015, at 10:24 AM, Andy Seaborne wrote:
>
> We have:
>
> * in-memory transactional dataset from Adam is in the codebase
> (details on progress below)
> * configurable lucene analyzers
> * general maintenance.
> * Improved start-up and configuration to wire the jars together.
>
> Shall we do a release? This fits our 3-6 months cycle.
>
> As we know, getting people to try unreleased builds has limited effect
> (generally for point-bug fixes, less so for new features) so my
> suggestion is to release soon as v3.0.1 and describe the in-memory
> transactional dataset as "RC". It's not fully integrated (test: Fuseki
> is not using it yet) and getting that done and stable isn't an instant
> task to do. At the same time, a release will let people try it.
>
> So we expose the in-memory transactional dataset at the API level now,
> introduce the deprecations so people can see what's coming, and
> complete/stabilize the integration to make a v3.1.0 in a few months time.
>
> Andy
>
>
> Progress on the in-memory transactional dataset
> https://pony-poc.apache.org/thread.html/Zj36f2pbaszgdnj
>
> If you want to try it, then DatasetFactory.createTxnMem() is the entry
> point.
>
>
>
> Outstanding tasks:
> * Dependency version management in jena-parent.
>
> Done
>
> * more testing [done], and the organisation of the tests
>
> Test done, organisation of tests is partially done. There is a wider
> tasks to organise the dataset tests we have into some sort of order but
> that's non-blocking.
>
> * documentation
> * code cleaning for deprecation of DatasetFactory.createMem
> * Same migration for DatasetGraphFactory.createMem
> * Fuseki integration
>
>
>
>>>
>>
>
Re: A release?
On 09/12/15 12:58, A. Soroka wrote:
Is it possible for non-committers to see that? I get a login dialog with the message
"ASF Committers”.
The HTML on staging is public - I don't use my id to log in.
curl http://jena.staging.apache.org/documentation/rdf/datasets.html
works from where I am - no password, no login.
Have you got a CMS image setup from another time? that can get things
confused. (note - http, not nttps)
Or the markdown:
https://svn.apache.org/repos/asf/jena/site/trunk/content/documentation/rdf/datasets.md
Andy
---
A. Soroka
The University of Virginia Library
On Dec 9, 2015, at 5:20 AM, Andy Seaborne wrote:
I put some documentation in at
http://jena.staging.apache.org/documentation/rdf/datasets.html
because the announcement needs to link to something. I hope I got it right.
This can be changed between releases -- the bytes aren't in the release itself.
(The file name was chosen so that more general text could go there and this
becomes a section of documentation about dataset usage in Jena)
Andy
On 08/12/15 14:53, A. Soroka wrote:
That should certainly “enlist” a number of RC testers. {grin}
I will stand by for bug fixes.
---
A. Soroka
The University of Virginia Library
On Dec 8, 2015, at 3:38 AM, Andy Seaborne wrote:
On 23/11/15 15:31, A. Soroka wrote:
A weightless +1 from me, of course! {grin} I’m excited to see this stuff get in
front of people.
I’m not sure what you mean by “Fuseki integration”, Andy. Do you mean to make
the new dataset impl available as an option in Fuseki (presumably in both the
web admin UI and the CLI for the standalone server)?
Fuseki should chnage to using the new in-memory txn dataset when creating new
in-memory setups. So the template-driven assemblers (UI) and from the command
line (--mem) will change. Existing setups are preserved because the template
is used to create an assembler when first used, not each start-up.
Andy
---
A. Soroka
The University of Virginia Library
On Nov 23, 2015, at 10:24 AM, Andy Seaborne wrote:
We have:
* in-memory transactional dataset from Adam is in the codebase
(details on progress below)
* configurable lucene analyzers
* general maintenance.
* Improved start-up and configuration to wire the jars together.
Shall we do a release? This fits our 3-6 months cycle.
As we know, getting people to try unreleased builds has limited effect (generally for
point-bug fixes, less so for new features) so my suggestion is to release soon as v3.0.1
and describe the in-memory transactional dataset as "RC". It's not fully
integrated (test: Fuseki is not using it yet) and getting that done and stable isn't an
instant task to do. At the same time, a release will let people try it.
So we expose the in-memory transactional dataset at the API level now,
introduce the deprecations so people can see what's coming, and
complete/stabilize the integration to make a v3.1.0 in a few months time.
Andy
Progress on the in-memory transactional dataset
https://pony-poc.apache.org/thread.html/Zj36f2pbaszgdnj
If you want to try it, then DatasetFactory.createTxnMem() is the entry point.
Outstanding tasks:
* Dependency version management in jena-parent.
Done
* more testing [done], and the organisation of the tests
Test done, organisation of tests is partially done. There is a wider tasks to
organise the dataset tests we have into some sort of order but that's
non-blocking.
* documentation
* code cleaning for deprecation of DatasetFactory.createMem
* Same migration for DatasetGraphFactory.createMem
* Fuseki integration
per-graph locking for dataset?
I now understand a little what I did not understand at all a few months ago:
how very hard the MRMW problem for RDF datasets is. So I’ve been casting about
for some simple ways to deliver cheap and very limited forms of MRMW that might
provide some “bang for the buck” for Jena users. One to which I keep coming
back is the idea of a dataset with per-graph transaction locking. In other
words, a dataset wherein each named graph has a SW lock and the dataset as a
whole can support MRMW, as long as every writer is working in a different
graph. Some examples of where this could be helpful:
* Linked Data persistence backends in which the graph about each
HTTP-accessible resource is stored in a separate named graph.
* Fast loading of quads from a sorted file (using multiple cursors).
* Persistence backends that use RDF (like the one that Claude recently
mentioned on users@) if they can be configured to take advantage of named
graphs.
Does this sound like it would be useful enough for me to spend some time
working out a design (after finishing what’s needed to RC-release the MR+SW
in-memory dataset)? I know we can never be sure about what users will find
handy until they start relying on it and praise it and complain about it…
{grin}
---
A. Soroka
The University of Virginia Library
Re: A release?
Okay, after trying three browsers, I found one that works (the others kept
redirecting to https). I have some suggestions (and some guilt, since I should
have written this without prompting). Shall I send a patch against the Markdown
in SVN?
---
A. Soroka
The University of Virginia Library
> On Dec 9, 2015, at 8:03 AM, Andy Seaborne wrote:
>
> On 09/12/15 12:58, A. Soroka wrote:
>> Is it possible for non-committers to see that? I get a login dialog with the
>> message "ASF Committers”.
>
> The HTML on staging is public - I don't use my id to log in.
>
> curl http://jena.staging.apache.org/documentation/rdf/datasets.html
>
> works from where I am - no password, no login.
>
> Have you got a CMS image setup from another time? that can get things
> confused. (note - http, not nttps)
>
> Or the markdown:
>
> https://svn.apache.org/repos/asf/jena/site/trunk/content/documentation/rdf/datasets.md
>
> Andy
>
>>
>> ---
>> A. Soroka
>> The University of Virginia Library
>>
>>> On Dec 9, 2015, at 5:20 AM, Andy Seaborne wrote:
>>>
>>> I put some documentation in at
>>>
>>> http://jena.staging.apache.org/documentation/rdf/datasets.html
>>>
>>> because the announcement needs to link to something. I hope I got it
>>> right. This can be changed between releases -- the bytes aren't in the
>>> release itself.
>>>
>>> (The file name was chosen so that more general text could go there and this
>>> becomes a section of documentation about dataset usage in Jena)
>>>
>>> Andy
>>>
>>> On 08/12/15 14:53, A. Soroka wrote:
That should certainly “enlist” a number of RC testers. {grin}
I will stand by for bug fixes.
---
A. Soroka
The University of Virginia Library
> On Dec 8, 2015, at 3:38 AM, Andy Seaborne wrote:
>
> On 23/11/15 15:31, A. Soroka wrote:
>> A weightless +1 from me, of course! {grin} I’m excited to see this stuff
>> get in front of people.
>>
>> I’m not sure what you mean by “Fuseki integration”, Andy. Do you mean to
>> make the new dataset impl available as an option in Fuseki (presumably
>> in both the web admin UI and the CLI for the standalone server)?
>
> Fuseki should chnage to using the new in-memory txn dataset when creating
> new in-memory setups. So the template-driven assemblers (UI) and from
> the command line (--mem) will change. Existing setups are preserved
> because the template is used to create an assembler when first used, not
> each start-up.
>
> Andy
>
>>
>> ---
>> A. Soroka
>> The University of Virginia Library
>>
>>> On Nov 23, 2015, at 10:24 AM, Andy Seaborne wrote:
>>>
>>> We have:
>>>
>>> * in-memory transactional dataset from Adam is in the codebase
>>> (details on progress below)
>>> * configurable lucene analyzers
>>> * general maintenance.
>>> * Improved start-up and configuration to wire the jars together.
>>>
>>> Shall we do a release? This fits our 3-6 months cycle.
>>>
>>> As we know, getting people to try unreleased builds has limited effect
>>> (generally for point-bug fixes, less so for new features) so my
>>> suggestion is to release soon as v3.0.1 and describe the in-memory
>>> transactional dataset as "RC". It's not fully integrated (test: Fuseki
>>> is not using it yet) and getting that done and stable isn't an instant
>>> task to do. At the same time, a release will let people try it.
>>>
>>> So we expose the in-memory transactional dataset at the API level now,
>>> introduce the deprecations so people can see what's coming, and
>>> complete/stabilize the integration to make a v3.1.0 in a few months
>>> time.
>>>
>>> Andy
>>>
>>>
>>> Progress on the in-memory transactional dataset
>>> https://pony-poc.apache.org/thread.html/Zj36f2pbaszgdnj
>>>
>>> If you want to try it, then DatasetFactory.createTxnMem() is the entry
>>> point.
>>>
>>>
>>>
>>> Outstanding tasks:
>>> * Dependency version management in jena-parent.
>>>
>>> Done
>>>
>>> * more testing [done], and the organisation of the tests
>>>
>>> Test done, organisation of tests is partially done. There is a wider
>>> tasks to organise the dataset tests we have into some sort of order but
>>> that's non-blocking.
>>>
>>> * documentation
>>> * code cleaning for deprecation of DatasetFactory.createMem
>>> * Same migration for DatasetGraphFactory.createMem
>>> * Fuseki integration
>>>
>>>
>>>
>>
>
>>>
>>
>
Re: A release?
Here:
https://gist.github.com/ajs6f/463117f0d0e094ffefc5
are some suggested edits for that doc, mostly just typo-fixes and suggestions
for clarification. Other questions from me:
1) Is it worth creating a component in Jira to track tickets for this stuff?
2) Shall I write up a simple page describing the impl and more importantly,
extension points?
---
A. Soroka
The University of Virginia Library
> On Dec 9, 2015, at 5:20 AM, Andy Seaborne wrote:
>
> I put some documentation in at
>
> http://jena.staging.apache.org/documentation/rdf/datasets.html
>
> because the announcement needs to link to something. I hope I got it right.
> This can be changed between releases -- the bytes aren't in the release
> itself.
>
> (The file name was chosen so that more general text could go there and this
> becomes a section of documentation about dataset usage in Jena)
>
> Andy
>
> On 08/12/15 14:53, A. Soroka wrote:
>> That should certainly “enlist” a number of RC testers. {grin}
>>
>> I will stand by for bug fixes.
>>
>> ---
>> A. Soroka
>> The University of Virginia Library
>>
>>> On Dec 8, 2015, at 3:38 AM, Andy Seaborne wrote:
>>>
>>> On 23/11/15 15:31, A. Soroka wrote:
A weightless +1 from me, of course! {grin} I’m excited to see this stuff
get in front of people.
I’m not sure what you mean by “Fuseki integration”, Andy. Do you mean to
make the new dataset impl available as an option in Fuseki (presumably in
both the web admin UI and the CLI for the standalone server)?
>>>
>>> Fuseki should chnage to using the new in-memory txn dataset when creating
>>> new in-memory setups. So the template-driven assemblers (UI) and from the
>>> command line (--mem) will change. Existing setups are preserved because
>>> the template is used to create an assembler when first used, not each
>>> start-up.
>>>
>>> Andy
>>>
---
A. Soroka
The University of Virginia Library
> On Nov 23, 2015, at 10:24 AM, Andy Seaborne wrote:
>
> We have:
>
> * in-memory transactional dataset from Adam is in the codebase
> (details on progress below)
> * configurable lucene analyzers
> * general maintenance.
> * Improved start-up and configuration to wire the jars together.
>
> Shall we do a release? This fits our 3-6 months cycle.
>
> As we know, getting people to try unreleased builds has limited effect
> (generally for point-bug fixes, less so for new features) so my
> suggestion is to release soon as v3.0.1 and describe the in-memory
> transactional dataset as "RC". It's not fully integrated (test: Fuseki
> is not using it yet) and getting that done and stable isn't an instant
> task to do. At the same time, a release will let people try it.
>
> So we expose the in-memory transactional dataset at the API level now,
> introduce the deprecations so people can see what's coming, and
> complete/stabilize the integration to make a v3.1.0 in a few months time.
>
> Andy
>
>
> Progress on the in-memory transactional dataset
> https://pony-poc.apache.org/thread.html/Zj36f2pbaszgdnj
>
> If you want to try it, then DatasetFactory.createTxnMem() is the entry
> point.
>
>
>
> Outstanding tasks:
> * Dependency version management in jena-parent.
>
> Done
>
> * more testing [done], and the organisation of the tests
>
> Test done, organisation of tests is partially done. There is a wider
> tasks to organise the dataset tests we have into some sort of order but
> that's non-blocking.
>
> * documentation
> * code cleaning for deprecation of DatasetFactory.createMem
> * Same migration for DatasetGraphFactory.createMem
> * Fuseki integration
>
>
>
>>>
>>
>
[jira] [Created] (JENA-1080) Fuseki Web Interface incompatible with Internet Explorer
Donald Pellegrino created JENA-1080: --- Summary: Fuseki Web Interface incompatible with Internet Explorer Key: JENA-1080 URL: https://issues.apache.org/jira/browse/JENA-1080 Project: Apache Jena Issue Type: Improvement Components: Fuseki Affects Versions: Fuseki 2.3.0 Environment: Microsoft Internet Explorer 11.0.9600.18097 Reporter: Donald Pellegrino Priority: Trivial Microsoft Internet Explorer 11 defaults to rendering Apache Jena Fuseki web pages in "Document mode 7." Using F12 and manually changing the "Document mode" to "Edge" seems to work-around the problem. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] jena pull request: JENA-1078: Logging warning when transaction is ...
Github user asfgit closed the pull request at: https://github.com/apache/jena/pull/105 --- 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] [Commented] (JENA-1078) TxnMem does not log a warning when commit() omitted.
[
https://issues.apache.org/jira/browse/JENA-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15049126#comment-15049126
]
ASF GitHub Bot commented on JENA-1078:
--
Github user asfgit closed the pull request at:
https://github.com/apache/jena/pull/105
> TxnMem does not log a warning when commit() omitted.
>
>
> Key: JENA-1078
> URL: https://issues.apache.org/jira/browse/JENA-1078
> Project: Apache Jena
> Issue Type: Bug
>Affects Versions: Jena 3.0.1
>Reporter: Andy Seaborne
> Fix For: Jena 3.1.0
>
>
> Example:
> {noformat}
> Dataset ds = DatasetFactory.createTxnMem() ;
> //Dataset ds = TDBFactory.createDataset() ;
> ds.begin(ReadWrite.WRITE) ;
> //ds.commit();
> ds.end() ;
> {noformat}
> whereas a read transaction can be:
> {noformat}
> Dataset ds = DatasetFactory.createTxnMem() ;
> ds.begin(ReadWrite.READ) ;
> ds.end() ;
> {noformat}
> See javadoc for {{org.apache.jena.sparql.core.Transactional}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (JENA-1078) TxnMem does not log a warning when commit() omitted.
[
https://issues.apache.org/jira/browse/JENA-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-1078.
-
Resolution: Fixed
Assignee: A. Soroka
> TxnMem does not log a warning when commit() omitted.
>
>
> Key: JENA-1078
> URL: https://issues.apache.org/jira/browse/JENA-1078
> Project: Apache Jena
> Issue Type: Bug
>Affects Versions: Jena 3.0.1
>Reporter: Andy Seaborne
>Assignee: A. Soroka
> Fix For: Jena 3.1.0
>
>
> Example:
> {noformat}
> Dataset ds = DatasetFactory.createTxnMem() ;
> //Dataset ds = TDBFactory.createDataset() ;
> ds.begin(ReadWrite.WRITE) ;
> //ds.commit();
> ds.end() ;
> {noformat}
> whereas a read transaction can be:
> {noformat}
> Dataset ds = DatasetFactory.createTxnMem() ;
> ds.begin(ReadWrite.READ) ;
> ds.end() ;
> {noformat}
> See javadoc for {{org.apache.jena.sparql.core.Transactional}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (JENA-1081) Turtle writer does not inline blank node in lists.
Andy Seaborne created JENA-1081:
---
Summary: Turtle writer does not inline blank node in lists.
Key: JENA-1081
URL: https://issues.apache.org/jira/browse/JENA-1081
Project: Apache Jena
Issue Type: Bug
Components: T, RIOT
Affects Versions: Jena 3.1.0
Reporter: Andy Seaborne
Priority: Minor
{noformat}
prefix :
[jira] [Updated] (JENA-1081) Turtle writer does not inline blank node in lists.
[
https://issues.apache.org/jira/browse/JENA-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-1081:
Description:
{noformat}
prefix :
was: per-graph locking for dataset?
On 09/12/15 13:22, A. Soroka wrote: (after finishing what’s needed to RC-release the MR+SW in-memory dataset) The build is done - the VOTE is open now. if the VOTE passes, that's it! JIRA and maven are already bumped 3.1.0 next with versions now building as 3.1.0-SNAPSHOT. Andy
Re: A release?
On 09/12/15 15:19, A. Soroka wrote:
Here:
https://gist.github.com/ajs6f/463117f0d0e094ffefc5
are some suggested edits for that doc, mostly just typo-fixes and suggestions
for clarification.
Done, thanks.
Other questions from me:
1) Is it worth creating a component in Jira to track tickets for this stuff?
I think incoming JIRAs won't be simple to associate with this one
component. We can see how it goes but the various differences in the
datasets are more likely the issues. Just a guess.
2) Shall I write up a simple page describing the impl and more importantly,
extension points?
Always useful, not urgent.
(What are the extension points?)
Andy
---
A. Soroka
The University of Virginia Library
On Dec 9, 2015, at 5:20 AM, Andy Seaborne wrote:
I put some documentation in at
http://jena.staging.apache.org/documentation/rdf/datasets.html
because the announcement needs to link to something. I hope I got it right.
This can be changed between releases -- the bytes aren't in the release itself.
(The file name was chosen so that more general text could go there and this
becomes a section of documentation about dataset usage in Jena)
Andy
On 08/12/15 14:53, A. Soroka wrote:
That should certainly “enlist” a number of RC testers. {grin}
I will stand by for bug fixes.
---
A. Soroka
The University of Virginia Library
On Dec 8, 2015, at 3:38 AM, Andy Seaborne wrote:
On 23/11/15 15:31, A. Soroka wrote:
A weightless +1 from me, of course! {grin} I’m excited to see this stuff get in
front of people.
I’m not sure what you mean by “Fuseki integration”, Andy. Do you mean to make
the new dataset impl available as an option in Fuseki (presumably in both the
web admin UI and the CLI for the standalone server)?
Fuseki should chnage to using the new in-memory txn dataset when creating new
in-memory setups. So the template-driven assemblers (UI) and from the command
line (--mem) will change. Existing setups are preserved because the template
is used to create an assembler when first used, not each start-up.
Andy
---
A. Soroka
The University of Virginia Library
On Nov 23, 2015, at 10:24 AM, Andy Seaborne wrote:
We have:
* in-memory transactional dataset from Adam is in the codebase
(details on progress below)
* configurable lucene analyzers
* general maintenance.
* Improved start-up and configuration to wire the jars together.
Shall we do a release? This fits our 3-6 months cycle.
As we know, getting people to try unreleased builds has limited effect (generally for
point-bug fixes, less so for new features) so my suggestion is to release soon as v3.0.1
and describe the in-memory transactional dataset as "RC". It's not fully
integrated (test: Fuseki is not using it yet) and getting that done and stable isn't an
instant task to do. At the same time, a release will let people try it.
So we expose the in-memory transactional dataset at the API level now,
introduce the deprecations so people can see what's coming, and
complete/stabilize the integration to make a v3.1.0 in a few months time.
Andy
Progress on the in-memory transactional dataset
https://pony-poc.apache.org/thread.html/Zj36f2pbaszgdnj
If you want to try it, then DatasetFactory.createTxnMem() is the entry point.
Outstanding tasks:
* Dependency version management in jena-parent.
Done
* more testing [done], and the organisation of the tests
Test done, organisation of tests is partially done. There is a wider tasks to
organise the dataset tests we have into some sort of order but that's
non-blocking.
* documentation
* code cleaning for deprecation of DatasetFactory.createMem
* Same migration for DatasetGraphFactory.createMem
* Fuseki integration
Re: A release?
Cool. The extension points are basically TripleTable and QuadTable, because of
the constructor DatasetGraphInMemory(QuadTable, TripleTable). Someone could
offer their own impls and use that (public) constructor.
---
A. Soroka
The University of Virginia Library
> On Dec 9, 2015, at 3:38 PM, Andy Seaborne wrote:
>
> On 09/12/15 15:19, A. Soroka wrote:
>> Here:
>>
>> https://gist.github.com/ajs6f/463117f0d0e094ffefc5
>>
>> are some suggested edits for that doc, mostly just typo-fixes and
>> suggestions for clarification.
>
> Done, thanks.
>
>> Other questions from me:
>>
>> 1) Is it worth creating a component in Jira to track tickets for this stuff?
>
> I think incoming JIRAs won't be simple to associate with this one component.
> We can see how it goes but the various differences in the datasets are more
> likely the issues. Just a guess.
>
>>
>> 2) Shall I write up a simple page describing the impl and more importantly,
>> extension points?
>
> Always useful, not urgent.
>
> (What are the extension points?)
>
> Andy
>
>>
>> ---
>> A. Soroka
>> The University of Virginia Library
>>
>>> On Dec 9, 2015, at 5:20 AM, Andy Seaborne wrote:
>>>
>>> I put some documentation in at
>>>
>>> http://jena.staging.apache.org/documentation/rdf/datasets.html
>>>
>>> because the announcement needs to link to something. I hope I got it
>>> right. This can be changed between releases -- the bytes aren't in the
>>> release itself.
>>>
>>> (The file name was chosen so that more general text could go there and this
>>> becomes a section of documentation about dataset usage in Jena)
>>>
>>> Andy
>>>
>>> On 08/12/15 14:53, A. Soroka wrote:
That should certainly “enlist” a number of RC testers. {grin}
I will stand by for bug fixes.
---
A. Soroka
The University of Virginia Library
> On Dec 8, 2015, at 3:38 AM, Andy Seaborne wrote:
>
> On 23/11/15 15:31, A. Soroka wrote:
>> A weightless +1 from me, of course! {grin} I’m excited to see this stuff
>> get in front of people.
>>
>> I’m not sure what you mean by “Fuseki integration”, Andy. Do you mean to
>> make the new dataset impl available as an option in Fuseki (presumably
>> in both the web admin UI and the CLI for the standalone server)?
>
> Fuseki should chnage to using the new in-memory txn dataset when creating
> new in-memory setups. So the template-driven assemblers (UI) and from
> the command line (--mem) will change. Existing setups are preserved
> because the template is used to create an assembler when first used, not
> each start-up.
>
> Andy
>
>>
>> ---
>> A. Soroka
>> The University of Virginia Library
>>
>>> On Nov 23, 2015, at 10:24 AM, Andy Seaborne wrote:
>>>
>>> We have:
>>>
>>> * in-memory transactional dataset from Adam is in the codebase
>>> (details on progress below)
>>> * configurable lucene analyzers
>>> * general maintenance.
>>> * Improved start-up and configuration to wire the jars together.
>>>
>>> Shall we do a release? This fits our 3-6 months cycle.
>>>
>>> As we know, getting people to try unreleased builds has limited effect
>>> (generally for point-bug fixes, less so for new features) so my
>>> suggestion is to release soon as v3.0.1 and describe the in-memory
>>> transactional dataset as "RC". It's not fully integrated (test: Fuseki
>>> is not using it yet) and getting that done and stable isn't an instant
>>> task to do. At the same time, a release will let people try it.
>>>
>>> So we expose the in-memory transactional dataset at the API level now,
>>> introduce the deprecations so people can see what's coming, and
>>> complete/stabilize the integration to make a v3.1.0 in a few months
>>> time.
>>>
>>> Andy
>>>
>>>
>>> Progress on the in-memory transactional dataset
>>> https://pony-poc.apache.org/thread.html/Zj36f2pbaszgdnj
>>>
>>> If you want to try it, then DatasetFactory.createTxnMem() is the entry
>>> point.
>>>
>>>
>>>
>>> Outstanding tasks:
>>> * Dependency version management in jena-parent.
>>>
>>> Done
>>>
>>> * more testing [done], and the organisation of the tests
>>>
>>> Test done, organisation of tests is partially done. There is a wider
>>> tasks to organise the dataset tests we have into some sort of order but
>>> that's non-blocking.
>>>
>>> * documentation
>>> * code cleaning for deprecation of DatasetFactory.createMem
>>> * Same migration for DatasetGraphFactory.createMem
>>> * Fuseki integration
>>>
>>>
>>>
>>
>
>>>
>>
>
