[jira] [Commented] (JENA-1088) Fuseki 2 allows duplicate datasets when using only spaces in name

[Andy Seaborne (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15072113#comment-15072113
 ] 

Andy Seaborne commented on JENA-1088:
-

Either way is fine - the server must be sufficiently defensive. I think the UI 
should be helpful (trim start/finish white space) but that's fine tuning. We 
have the basic "it does not go wrong" fix.  I'll leave it to your judgement.

(On UIs : but then I don't see why websites insist on no spaces credit card 
numbers when they are printed on cards with spaces every 4 numbers, at least in 
the UK they are. Similarly phone numbers.)

> Fuseki 2 allows duplicate datasets when using only spaces in name
> -
>
> Key: JENA-1088
> URL: https://issues.apache.org/jira/browse/JENA-1088
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Fuseki
>Reporter: Bruno P. Kinoshita
>Assignee: Andy Seaborne
>  Labels: web
> Attachments: JENA-1088.png, Jena-1088-AFS-1.patch
>
>   Original Estimate: 2h
>  Time Spent: 2h
>  Remaining Estimate: 0h
>
> Was testing Fuseki 2, before reviewing the docs, and decided to experiment a 
> few things. Looks like if you use just spaces in the dataset name, you are 
> allowed to create a new one, and it gets the name "/". Which is fine.
> But if you try that again with another random number of spaces, it inserts 
> another dataset with the same name.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JENA-632) Generate JSON from SPARQL directly.

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15072118#comment-15072118
 ] 

ASF GitHub Bot commented on JENA-632:
-

GitHub user kinow opened a pull request:

https://github.com/apache/jena/pull/114

JENA-632: Generate JSON from SPARQL directly

This pull request contains code for 
[JENA-632](https://issues.apache.org/jira/browse/JENA-632). The original work 
is still in a branch in [my fork of 
Jena](https://github.com/apache/jena/compare/master...kinow:JENA-632). It has 
been updated after the work on Jena 3 (mainly package renaming). And the web 
layer has been implemented in fuseki 2, but not backported to fuseki 1.

Besides reviewing the code, the follow steps can be used to quickly test 
the code.

* Start Fuseki (debug in Eclipse after checking out this branch, for 
example)
* Load the books.ttl from fuseki1/Data directory
* Query with something as

```
PREFIX purl: 
PREFIX w3:  
PREFIX :  

JSON {
"author": ?author, 
"title": ?title 
}
WHERE 
{
?book purl:creator ?author .
?book purl:title ?title . 
FILTER (?author = 'J.K. Rowling')
}
```

Which follows the syntax proposed in the issue in JIRA.

I am still reviewing the code after porting to the new code base, but an 
extra pair of eyes reviewing it is always welcome! :grin: 

ps: the SPARQL editor may need some tweaking to support the new syntax

ps2: tried to change the key name in the JSON query but it didn't work. 
Will try to update the PR if that's really a bug in the code in the next days

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/kinow/jena JENA-632-2

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/jena/pull/114.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #114


commit 0049f2abcb757c9a190e0017d9369583f4eebf93
Author: Bruno P. Kinoshita 
Date:   2015-12-27T10:51:24Z

JENA-632: Generate JSON from SPARQL directly




> Generate JSON from SPARQL directly.
> ---
>
> Key: JENA-632
> URL: https://issues.apache.org/jira/browse/JENA-632
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: ARQ, Fuseki
>Reporter: Andy Seaborne
>Assignee: Bruno P. Kinoshita
>Priority: Minor
>  Labels: java, javacc
>
> The capability to generate JSON directly from a SPARQL (or extended SPARQL) 
> query would enable the creation of JSON data API over published linked data.
> This project would cover:
> # Design and publication of a design.
> # Refinement of design based on community feed
> # Implementation, including testing.
> # Refinement of implementation based on community feed
> Skills required: Java, some parser work, design and discussion with the user 
> community, basic understanding of HTTP and content negotiation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] jena pull request: JENA-632: Generate JSON from SPARQL directly

[kinow]

GitHub user kinow opened a pull request:

https://github.com/apache/jena/pull/114

JENA-632: Generate JSON from SPARQL directly

This pull request contains code for 
[JENA-632](https://issues.apache.org/jira/browse/JENA-632). The original work 
is still in a branch in [my fork of 
Jena](https://github.com/apache/jena/compare/master...kinow:JENA-632). It has 
been updated after the work on Jena 3 (mainly package renaming). And the web 
layer has been implemented in fuseki 2, but not backported to fuseki 1.

Besides reviewing the code, the follow steps can be used to quickly test 
the code.

* Start Fuseki (debug in Eclipse after checking out this branch, for 
example)
* Load the books.ttl from fuseki1/Data directory
* Query with something as

```
PREFIX purl: 
PREFIX w3:  
PREFIX :  

JSON {
"author": ?author, 
"title": ?title 
}
WHERE 
{
?book purl:creator ?author .
?book purl:title ?title . 
FILTER (?author = 'J.K. Rowling')
}
```

Which follows the syntax proposed in the issue in JIRA.

I am still reviewing the code after porting to the new code base, but an 
extra pair of eyes reviewing it is always welcome! :grin: 

ps: the SPARQL editor may need some tweaking to support the new syntax

ps2: tried to change the key name in the JSON query but it didn't work. 
Will try to update the PR if that's really a bug in the code in the next days

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/kinow/jena JENA-632-2

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/jena/pull/114.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #114


commit 0049f2abcb757c9a190e0017d9369583f4eebf93
Author: Bruno P. Kinoshita 
Date:   2015-12-27T10:51:24Z

JENA-632: Generate JSON from SPARQL directly




---
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-1080) Fuseki Web Interface incompatible with Internet Explorer

[Andy Seaborne (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15072122#comment-15072122
 ] 

Andy Seaborne commented on JENA-1080:
-

[~donpellegrino] - if you get a chance to try this, we'd be most grateful.

Personal view - commit it and it will get into a snapshot build which will make 
it easier. We have git - it can be reverted! 

We are more likely to get feedback that way as a few people use snapshots to 
pick up immediate bug fixes. The alternative is people getting it at release 
time.


> 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
>Assignee: Bruno P. Kinoshita
>Priority: Trivial
>  Labels: windows
> Attachments: JENA-1080-001.png, JENA-1080-002.png, JENA-1080-003.png, 
> JENA-1080-004.png
>
>
> 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)

[jira] [Commented] (JENA-806) illegal escape sequence value exception on legal characters

[MonKey Lee (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15072141#comment-15072141
 ] 

MonKey Lee commented on JENA-806:
-

Tracked at [Wikidata-Toolkit :: Issue 
#199|https://github.com/Wikidata/Wikidata-Toolkit/issues/199]

> illegal escape sequence value exception on legal characters
> ---
>
> Key: JENA-806
> URL: https://issues.apache.org/jira/browse/JENA-806
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Cmd line tools
>Affects Versions: Jena 2.12.1
> Environment: Ubuntu 14.04, Java 8
>Reporter: Nick Lothian
>Assignee: Andy Seaborne
>
> When loading the Wikidata data dump using tdbloader2, I received the 
> following error:
> {{ERROR [line: 142128, col: 121] illegal escape sequence value: " (0x22)
> org.apache.jena.riot.RiotException: [line: 142128, col: 121] illegal escape 
> sequence value: " (0x22)
> at 
> org.apache.jena.riot.system.ErrorHandlerFactory$ErrorHandlerStd.fatal(ErrorHandlerFactory.java:136)
> at 
> org.apache.jena.riot.lang.LangEngine.raiseException(LangEngine.java:163)
> at org.apache.jena.riot.lang.LangEngine.nextToken(LangEngine.java:106)
> at 
> org.apache.jena.riot.lang.LangNTriples.parseOne(LangNTriples.java:67)
> at 
> org.apache.jena.riot.lang.LangNTriples.runParser(LangNTriples.java:54)
> at org.apache.jena.riot.lang.LangBase.parse(LangBase.java:42)
> at org.apache.jena.riot.RiotReader.parse(RiotReader.java:119)
> at org.apache.jena.riot.RiotReader.parse(RiotReader.java:96)
> at org.apache.jena.riot.RiotReader.parse(RiotReader.java:69)
> at 
> com.hp.hpl.jena.tdb.store.bulkloader2.CmdNodeTableBuilder.exec(CmdNodeTableBuilder.java:162)
> at arq.cmdline.CmdMain.mainMethod(CmdMain.java:102)
> at arq.cmdline.CmdMain.mainRun(CmdMain.java:63)
> at arq.cmdline.CmdMain.mainRun(CmdMain.java:50)
> at 
> com.hp.hpl.jena.tdb.store.bulkloader2.CmdNodeTableBuilder.main(CmdNodeTableBuilder.java:80)
> }}
> Looking that that line 
> {{sed '142128!d' uncompressed/wikidata-simple-statements.nt}}
> {{ 
>  
> 
>  .}}
> Column 121 is the "R" after the ". 
> Looking at http://www.w3.org/TR/n-triples/#n-triples-grammar, it appears that 
> the " character is allowed.
> Should tdbloader2 load this or am I missing something?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (JENA-1101) Fuseki filesystem layout and Linux FHS

[Andy Seaborne (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JENA-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andy Seaborne resolved JENA-1101.
-
Resolution: Won't Fix

Centos-centric proposal.

> Fuseki filesystem layout and Linux FHS
> --
>
> Key: JENA-1101
> URL: https://issues.apache.org/jira/browse/JENA-1101
> Project: Apache Jena
>  Issue Type: Improvement
>Affects Versions: Fuseki 2.3.1
>Reporter: Joachim Neubert
>
> When it comes to filesystem layout, the Java/Tomcat/Webapps world differs 
> quite fundamentally from the Linux world: Whereas for Tomcat or Fuseki it is 
> quite normal to have all files under a common root directory, the [Linux 
> Filesystem Hierarchy 
> Standard|https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard] (which 
> is followed by most distributions) provides multiple roots for application 
> files:
> Configuration goes to /etc, read-only files to /usr, variable files to /var 
> (./log, ./cache etc.). To give you a better idea what this means in practice, 
> I add the layout of the tomcat installation by Centos 7 RPM as an example.
> From a linux sysadmins point of view, this makes it easy to know where to 
> find stuff without any special knowledge of the application, and to 
> generalize tasks like backup (e.g. exclude all application cache files on the 
> system).
> On the other hand, this means considerable more work, if you have to cover 
> systems outside the Linux world too. Things may get even more complicated by 
> remaining differeces between distributions and SElinux policies.
> So I don't suppose FHS compatibility is an realistic option for Fuseki.
> Yet, the current handling of mapping $FUSEKI_HOME/run to /etc/fuseki, with 
> the whole bunch of assorted runtime files, feels profundly wrong. According 
> to FHS, I would expect something like
> {noformat}
> etc/
>   fuseki/
> config.ttl
> shiro.ttl
> conf.d/
>   service1.ttl
>   ...
> {noformat}
> and all the other stuff elsewhere.
> So I wonder if it would be possible to put the config hierarchy above under 
> a, say, $FUSEKI_CONF root, which defaults to /etc/fuseki in the .war 
> installation, and to $FUSEKI/conf otherwise.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [jena-jdbc] Need to call ARQ.init() before using TDBDriver

[Andy Seaborne]

Good to know the root cause.

The default choice for Java's ServiceLoader.load is the current thread 
classloader.  If we could be sure what the other classloader has to be, 
we could wrap this into some nice API call.  But I can image its quite 
tricky to safely find the classloader in a portable way without risking 
initialization in some environments.


(The JenaSubsystemRegistry is settable if the app does it early enough.)

Inline 

On 24/12/15 23:41, Bruno P. Kinoshita wrote:

Hi again;

I think I found the answer for that. Here's the commit 
https://github.com/biouno/database-sparql-plugin/blob/3cdc90c0da4fc71e44876b103b0e942fe7e975bd/src/main/java/org/biouno/databasesparql/JenaTDBDatabase.java#L73

When loading plug-ins, I believe Jenkins does some magic with the class loader 
(probably for the whole plugin strategy, but probably also for security, class 
loading conflict, etc). So after looking for a while I found a short thread 
from 2010 [1]

After switching the context class loader as suggested in the e-mail thread, I 
believe the Jena initialisation worked as expected

INFO: Loaded all jobsJenaSystem.init - start  InitRIOT  InitARQ  InitTDB  
InitJenaCoreInit: JenaInitLevel0Init: InitJenaCoreJenaCore.init - 
startJenaCore.init - finishInit: InitRIOTRIOT.init - startRIOT.init - 
finishInit: InitARQARQ.init - startARQ.init - finishInit: InitTDBTDB.init - 
startTDB.init - finishJenaSystem.init - finish

If there are no objections I will add an extra section in the bottom of the 
Jena Initialization notes about applications with multiple classloaders that 
use Jena, explaining that it may be necessary to switch the context classloader 
in order for the ServiceLocator to work correctly.


Sounds like a good plan.

Andy



Thanks!Bruno

[1] http://jenkins-ci.361315.n4.nabble.com/ClassLoader-in-plugins-td1470791.html



   From: Bruno P. Kinoshita 
  To: "dev@jena.apache.org" 
  Sent: Friday, 25 December 2015 11:27 AM
  Subject: Re: [jena-jdbc] Need to call ARQ.init() before using TDBDriver

Hi Andy

Updated the gist (https://gist.github.com/kinow/efec3e14764f9cc002df) with the 
complete log after doing as you suggested (removed ARQ.init(), enabled debug).

But the only thing I could see in the console output in Eclipse was:

INFO: Loaded all jobs
JenaSystem.init - start
Init: JenaInitLevel0
JenaSystem.init - finish

Debugging that, I found the static constructor in the TDBDriver, calling 
JenaSystem.init(). However, after importing Jena src and debugging it, looks 
like the ServiceLoader is not able to find any implementations, so the context 
is completely empty (JenaInitLevel0 gets added later on).

Not sure if it's happening because of some incompatibility with Jenkins API, or 
because of the way that Jenkins plug-ins work. Any idea why the ServiceLoader 
would not find the JenaSubsystemLifecycle implementations?

Thank youBruno
ps: two trivial typos fixed in the documentation notes about jena 
initialization in r1721654 for jena-site


   From: Andy Seaborne 
  To: dev@jena.apache.org
  Sent: Friday, 25 December 2015 4:00 AM
  Subject: Re: [jena-jdbc] Need to call ARQ.init() before using TDBDriver

On 24/12/15 11:01, Bruno P. Kinoshita wrote:

Hi,

I am writing a plug-in for Jenkins to collect metadata about builds and store 
in Jena TDB. Then will a SPARQL Endpoint to Jenkins (not sure how yet, probably 
will init a Fuseki server within Jenkins).

An initial experimentation is to extend the Database Plugin to support SPARQL. 
The Database Plugin in Jenkins uses JDBC, so I decided to use jena-jdbc. 
However, when validating the connection I'm getting the following exception 
(full log in https://gist.github.com/kinow/efec3e14764f9cc002df).

Caused by: java.lang.NullPointerException at 
org.apache.jena.tdb.sys.SystemTDB.determineFileMode(SystemTDB.java:381) at 
org.apache.jena.tdb.sys.SystemTDB.fileMode(SystemTDB.java:356) at 
org.apache.jena.tdb.setup.StoreParamsConst.(StoreParamsConst.java:37) 
... 70 more

Looks like it depends on a context being initialised in ARQ beforehand. After 
adding a call to ARQ.init ([1]) the plug-in worked fine, and I could validate 
the connection. But I couldn't find any mention to ARQ.init in the 
documentation that I used from jena-jdbc ([2], [3]).

I used jena-jdbc in the past with Squirrel SQL, but I believe it was using the 
remote driver, so this is the first time I use the jena-jdbc-tdb-driver. If 
someone could confirm whether ARQ.init is necessary, I will update the 
documentation (or in case it's not, I can create an issue for that).

ThanksBruno

[1] 
https://github.com/biouno/database-sparql-plugin/blob/5827fc1e5397ce745639a8bd4d9ed19e24588cc6/src/main/java/org/biouno/databasesparql/JenaTDBDatabase.java#L40
[2] https://jena.apache.org/documentation/jdbc/

[3] https://jena.apache.org/documentation/jdbc/drivers.html#tdb



Hi Bruno,

About initialization:
http://jena.apache.org/documentation/notes/system-initialization.html

JenaSyst

[jira] [Created] (JENA-1107) Rework jena-base lib.Tuple

[Andy Seaborne (JIRA)]

Andy Seaborne created JENA-1107:
---

 Summary: Rework jena-base lib.Tuple
 Key: JENA-1107
 URL: https://issues.apache.org/jira/browse/JENA-1107
 Project: Apache Jena
  Issue Type: Improvement
Reporter: Andy Seaborne
Assignee: Andy Seaborne
Priority: Minor


Tuples, which are immutable, value-equality fixed length sequences of instances 
of the same type, accessed by index.

They are like {{T[]}} but immutable, with .equals based on contents, could be 
improved to work independently of their original use in TDB.

Proposal:

#  Make Tuple an interface (simpler than current), with special implementations 
for low number of elements.
# {{ColumnMap}} ==> {{TupleMap}} and sort out the naming as much as possible to 
use as a way to manage index mapping, not just rewriting Tuples.

An intermediate step is to move {{ColumnMap}} into TDB.

This is not a proposal to add it to {{Triple}} or {{Quad}}.

{{Triple}} is not the same as a 3-length {{Tuple}}.  Triple elements are 
accessed by name (`getSubject` etc) not index.  SPO is just one possible order 
in which to think about triples but it has no special status. 




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (JENA-1107) Improve jena-base lib.Tuple

[Andy Seaborne (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JENA-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andy Seaborne updated JENA-1107:

Summary: Improve jena-base lib.Tuple  (was: Rework jena-base lib.Tuple)

> Improve jena-base lib.Tuple
> ---
>
> Key: JENA-1107
> URL: https://issues.apache.org/jira/browse/JENA-1107
> Project: Apache Jena
>  Issue Type: Improvement
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
>
> Tuples, which are immutable, value-equality fixed length sequences of 
> instances of the same type, accessed by index.
> They are like {{T[]}} but immutable, with .equals based on contents, could be 
> improved to work independently of their original use in TDB.
> Proposal:
> #  Make Tuple an interface (simpler than current), with special 
> implementations for low number of elements.
> # {{ColumnMap}} ==> {{TupleMap}} and sort out the naming as much as possible 
> to use as a way to manage index mapping, not just rewriting Tuples.
> An intermediate step is to move {{ColumnMap}} into TDB.
> This is not a proposal to add it to {{Triple}} or {{Quad}}.
> {{Triple}} is not the same as a 3-length {{Tuple}}.  Triple elements 
> are accessed by name (`getSubject` etc) not index.  SPO is just one possible 
> order in which to think about triples but it has no special status. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (JENA-1107) Improve jena-base lib.Tuple

[Andy Seaborne (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JENA-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andy Seaborne updated JENA-1107:

Description: 
Tuples, which are immutable, value-equality fixed length sequences of instances 
of the same type, accessed by index.

They are like {{T[]}} but immutable, with .equals based on contents, and could 
be improved to work independently of their original use in TDB.

Proposal:

#  Make Tuple an interface (simpler than current), with special implementations 
for low number of elements.
# {{ColumnMap}} ==> {{TupleMap}} and sort out the naming as much as possible to 
use as a way to manage index mapping, not just rewriting Tuples.

An intermediate step is to move {{ColumnMap}} into TDB.

This is not a proposal to add it to {{Triple}} or {{Quad}}.

{{Triple}} is not the same as a 3-length {{Tuple}}.  Triple elements are 
accessed by name ({{getSubject}} etc), not index.  SPO is just one possible 
order in which to think about triples but it has no special status. 


  was:
Tuples, which are immutable, value-equality fixed length sequences of instances 
of the same type, accessed by index.

They are like {{T[]}} but immutable, with .equals based on contents, could be 
improved to work independently of their original use in TDB.

Proposal:

#  Make Tuple an interface (simpler than current), with special implementations 
for low number of elements.
# {{ColumnMap}} ==> {{TupleMap}} and sort out the naming as much as possible to 
use as a way to manage index mapping, not just rewriting Tuples.

An intermediate step is to move {{ColumnMap}} into TDB.

This is not a proposal to add it to {{Triple}} or {{Quad}}.

{{Triple}} is not the same as a 3-length {{Tuple}}.  Triple elements are 
accessed by name ({{getSubject}} etc), not index.  SPO is just one possible 
order in which to think about triples but it has no special status. 



> Improve jena-base lib.Tuple
> ---
>
> Key: JENA-1107
> URL: https://issues.apache.org/jira/browse/JENA-1107
> Project: Apache Jena
>  Issue Type: Improvement
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
>
> Tuples, which are immutable, value-equality fixed length sequences of 
> instances of the same type, accessed by index.
> They are like {{T[]}} but immutable, with .equals based on contents, and 
> could be improved to work independently of their original use in TDB.
> Proposal:
> #  Make Tuple an interface (simpler than current), with special 
> implementations for low number of elements.
> # {{ColumnMap}} ==> {{TupleMap}} and sort out the naming as much as possible 
> to use as a way to manage index mapping, not just rewriting Tuples.
> An intermediate step is to move {{ColumnMap}} into TDB.
> This is not a proposal to add it to {{Triple}} or {{Quad}}.
> {{Triple}} is not the same as a 3-length {{Tuple}}.  Triple elements 
> are accessed by name ({{getSubject}} etc), not index.  SPO is just one 
> possible order in which to think about triples but it has no special status. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (JENA-1107) Improve jena-base lib.Tuple

[Andy Seaborne (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JENA-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andy Seaborne updated JENA-1107:

Description: 
Tuples, which are immutable, value-equality fixed length sequences of instances 
of the same type, accessed by index.

They are like {{T[]}} but immutable, with .equals based on contents, could be 
improved to work independently of their original use in TDB.

Proposal:

#  Make Tuple an interface (simpler than current), with special implementations 
for low number of elements.
# {{ColumnMap}} ==> {{TupleMap}} and sort out the naming as much as possible to 
use as a way to manage index mapping, not just rewriting Tuples.

An intermediate step is to move {{ColumnMap}} into TDB.

This is not a proposal to add it to {{Triple}} or {{Quad}}.

{{Triple}} is not the same as a 3-length {{Tuple}}.  Triple elements are 
accessed by name ({{getSubject}} etc), not index.  SPO is just one possible 
order in which to think about triples but it has no special status. 


  was:
Tuples, which are immutable, value-equality fixed length sequences of instances 
of the same type, accessed by index.

They are like {{T[]}} but immutable, with .equals based on contents, could be 
improved to work independently of their original use in TDB.

Proposal:

#  Make Tuple an interface (simpler than current), with special implementations 
for low number of elements.
# {{ColumnMap}} ==> {{TupleMap}} and sort out the naming as much as possible to 
use as a way to manage index mapping, not just rewriting Tuples.

An intermediate step is to move {{ColumnMap}} into TDB.

This is not a proposal to add it to {{Triple}} or {{Quad}}.

{{Triple}} is not the same as a 3-length {{Tuple}}.  Triple elements are 
accessed by name (`getSubject` etc) not index.  SPO is just one possible order 
in which to think about triples but it has no special status. 



> Improve jena-base lib.Tuple
> ---
>
> Key: JENA-1107
> URL: https://issues.apache.org/jira/browse/JENA-1107
> Project: Apache Jena
>  Issue Type: Improvement
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
>
> Tuples, which are immutable, value-equality fixed length sequences of 
> instances of the same type, accessed by index.
> They are like {{T[]}} but immutable, with .equals based on contents, could be 
> improved to work independently of their original use in TDB.
> Proposal:
> #  Make Tuple an interface (simpler than current), with special 
> implementations for low number of elements.
> # {{ColumnMap}} ==> {{TupleMap}} and sort out the naming as much as possible 
> to use as a way to manage index mapping, not just rewriting Tuples.
> An intermediate step is to move {{ColumnMap}} into TDB.
> This is not a proposal to add it to {{Triple}} or {{Quad}}.
> {{Triple}} is not the same as a 3-length {{Tuple}}.  Triple elements 
> are accessed by name ({{getSubject}} etc), not index.  SPO is just one 
> possible order in which to think about triples but it has no special status. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JENA-1080) Fuseki Web Interface incompatible with Internet Explorer

[Donald Pellegrino (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15072195#comment-15072195
 ] 

Donald Pellegrino commented on JENA-1080:
-

Thanks for the quick fix. I will test on January 4, 2016 and post the results.

> 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
>Assignee: Bruno P. Kinoshita
>Priority: Trivial
>  Labels: windows
> Attachments: JENA-1080-001.png, JENA-1080-002.png, JENA-1080-003.png, 
> JENA-1080-004.png
>
>
> 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)

[jira] [Commented] (JENA-1107) Improve jena-base lib.Tuple

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15072198#comment-15072198
 ] 

ASF subversion and git services commented on JENA-1107:
---

Commit d95df6fcd841a713ac041dc1439aff51d99095ca in jena's branch 
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=d95df6f ]

JENA-1107: Move ColumnMap into TDB.

> Improve jena-base lib.Tuple
> ---
>
> Key: JENA-1107
> URL: https://issues.apache.org/jira/browse/JENA-1107
> Project: Apache Jena
>  Issue Type: Improvement
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
>
> Tuples, which are immutable, value-equality fixed length sequences of 
> instances of the same type, accessed by index.
> They are like {{T[]}} but immutable, with .equals based on contents, and 
> could be improved to work independently of their original use in TDB.
> Proposal:
> #  Make Tuple an interface (simpler than current), with special 
> implementations for low number of elements.
> # {{ColumnMap}} ==> {{TupleMap}} and sort out the naming as much as possible 
> to use as a way to manage index mapping, not just rewriting Tuples.
> An intermediate step is to move {{ColumnMap}} into TDB.
> This is not a proposal to add it to {{Triple}} or {{Quad}}.
> {{Triple}} is not the same as a 3-length {{Tuple}}.  Triple elements 
> are accessed by name ({{getSubject}} etc), not index.  SPO is just one 
> possible order in which to think about triples but it has no special status. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (JENA-1082) Add to org.apache.jena.rdf.model.ModelCon interface a listLiteralStatements method that accepts ints.

[Andy Seaborne (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069651#comment-15069651
 ] 

Andy Seaborne edited comment on JENA-1082 at 12/27/15 6:24 PM:
---

Are you storing the RDF in-memory?

If so, there is a different thing going on.  The {{listLiteralStatements}} is 
finding {{v:num}} based on value, not on the term (lexical forma + datatype).  
if you ask for 200(int) it will list 200\^^xsd:long, or 200\^^xsd:integer, or 
200\^^xsd:nonNegativeInteger or several others.  If you care about the 
presentation, you need to check the datatype as well.  Relying on the java 
basic type mapping to RDF datatype is unreliable as it is not perfect and 
two-way.



was (Author: andy.seaborne):
Are you storing the RDF in-memory?

If so, there is a different thing going on.  The {{listLiteralStatements}} is 
finding {{v:num}} based on value, not on the term (lexical forma + datatype).  
if you ask for 200(int) it will list 200^^xsd:long, or 200^^xsd:integer, or 
200^^xsd:nonNegativeInteger or several others.  If you care about the 
presentation, you need to check the datatype as well.  Relying on the java 
basic type mapping to RDF datatype is unreliable as it is not perfect and 
two-way.


> Add to org.apache.jena.rdf.model.ModelCon interface a listLiteralStatements 
> method that accepts ints.
> -
>
> Key: JENA-1082
> URL: https://issues.apache.org/jira/browse/JENA-1082
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: Jena 3.0.0
>Reporter: Ramiro Pereira de Magalhães
>Priority: Minor
>
> Add to org.apache.jena.rdf.model.ModelCon interface a {{StmtIterator 
> listLiteralStatements(Resource subject, Property predicate, int object );}} 
> method.
> Implement such method in classes that implement such interface. This method 
> should be able to list literal integer statements, like the other 
> listLiteralStatement methods do to other types.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JENA-1080) Fuseki Web Interface incompatible with Internet Explorer

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15072253#comment-15072253
 ] 

ASF subversion and git services commented on JENA-1080:
---

Commit 1bbe9ecdb3da6517aa3346b8eb67f902a3237b32 in jena's branch 
refs/heads/master from [~brunodepau...@yahoo.com.br]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=1bbe9ec ]

JENA-1080: add HTML meta tag to force edge mode in IE


> 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
>Assignee: Bruno P. Kinoshita
>Priority: Trivial
>  Labels: windows
> Attachments: JENA-1080-001.png, JENA-1080-002.png, JENA-1080-003.png, 
> JENA-1080-004.png
>
>
> 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)

[jira] [Commented] (JENA-1080) Fuseki Web Interface incompatible with Internet Explorer

[Bruno P. Kinoshita (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15072255#comment-15072255
 ] 

Bruno P. Kinoshita commented on JENA-1080:
--

>Personal view - commit it and it will get into a snapshot build which will 
>make it easier. We have git - it can be reverted!
>
>We are more likely to get feedback that way as a few people use snapshots to 
>pick up immediate bug fixes. The alternative is people getting it at release 
>time.

+1, committed in 1bbe9ecdb3da6517aa3346b8eb67f902a3237b32 :-)

> 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
>Assignee: Bruno P. Kinoshita
>Priority: Trivial
>  Labels: windows
> Attachments: JENA-1080-001.png, JENA-1080-002.png, JENA-1080-003.png, 
> JENA-1080-004.png
>
>
> 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)

[jira] [Commented] (JENA-1080) Fuseki Web Interface incompatible with Internet Explorer

[Bruno P. Kinoshita (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15072257#comment-15072257
 ] 

Bruno P. Kinoshita commented on JENA-1080:
--

That's great Donald! The change has been committed, so you have a few different 
ways to test it. If you can manually edit the HTML pages (you may have to 
restart Tomcat, or Fuseki) you can add the HTML meta tag missing. Or 
alternatively, you can grab a snapshot built after today (28/Dec/2015 21:49 
UTC), or build from sources. Hope that works, and thanks for testing it.

> 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
>Assignee: Bruno P. Kinoshita
>Priority: Trivial
>  Labels: windows
> Attachments: JENA-1080-001.png, JENA-1080-002.png, JENA-1080-003.png, 
> JENA-1080-004.png
>
>
> 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)

Re: [jena-jdbc] Need to call ARQ.init() before using TDBDriver

[Bruno P. Kinoshita]

I guess just having documentation somewhere is already sufficient, as very few 
users will face this problem.
Committed a simple section in the system initialization notes in r1721852 - 
http://jena.staging.apache.org/documentation/notes/system-initialization.html
Thanks for the help Andy!

 Bruno

 
  From: Andy Seaborne 
 To: dev@jena.apache.org 
 Sent: Monday, 28 December 2015 5:52 AM
 Subject: Re: [jena-jdbc] Need to call ARQ.init() before using TDBDriver
   
Good to know the root cause.

The default choice for Java's ServiceLoader.load is the current thread 
classloader.  If we could be sure what the other classloader has to be, 
we could wrap this into some nice API call.  But I can image its quite 
tricky to safely find the classloader in a portable way without risking 
initialization in some environments.

(The JenaSubsystemRegistry is settable if the app does it early enough.)

Inline 

On 24/12/15 23:41, Bruno P. Kinoshita wrote:
> Hi again;
>
> I think I found the answer for that. Here's the commit 
> https://github.com/biouno/database-sparql-plugin/blob/3cdc90c0da4fc71e44876b103b0e942fe7e975bd/src/main/java/org/biouno/databasesparql/JenaTDBDatabase.java#L73
>
> When loading plug-ins, I believe Jenkins does some magic with the class 
> loader (probably for the whole plugin strategy, but probably also for 
> security, class loading conflict, etc). So after looking for a while I found 
> a short thread from 2010 [1]
>
> After switching the context class loader as suggested in the e-mail thread, I 
> believe the Jena initialisation worked as expected
>
> INFO: Loaded all jobsJenaSystem.init - start  InitRIOT  InitARQ  InitTDB  
> InitJenaCoreInit: JenaInitLevel0Init: InitJenaCoreJenaCore.init - 
> startJenaCore.init - finishInit: InitRIOTRIOT.init - startRIOT.init - 
> finishInit: InitARQARQ.init - startARQ.init - finishInit: InitTDBTDB.init - 
> startTDB.init - finishJenaSystem.init - finish
>
> If there are no objections I will add an extra section in the bottom of the 
> Jena Initialization notes about applications with multiple classloaders that 
> use Jena, explaining that it may be necessary to switch the context 
> classloader in order for the ServiceLocator to work correctly.

Sounds like a good plan.

    Andy

>
> Thanks!Bruno
>
> [1] 
> http://jenkins-ci.361315.n4.nabble.com/ClassLoader-in-plugins-td1470791.html
>
>
>
>        From: Bruno P. Kinoshita 
>  To: "dev@jena.apache.org" 
>  Sent: Friday, 25 December 2015 11:27 AM
>  Subject: Re: [jena-jdbc] Need to call ARQ.init() before using TDBDriver
>
> Hi Andy
>
> Updated the gist (https://gist.github.com/kinow/efec3e14764f9cc002df) with 
> the complete log after doing as you suggested (removed ARQ.init(), enabled 
> debug).
>
> But the only thing I could see in the console output in Eclipse was:
>
> INFO: Loaded all jobs
> JenaSystem.init - start
> Init: JenaInitLevel0
> JenaSystem.init - finish
>
> Debugging that, I found the static constructor in the TDBDriver, calling 
> JenaSystem.init(). However, after importing Jena src and debugging it, looks 
> like the ServiceLoader is not able to find any implementations, so the 
> context is completely empty (JenaInitLevel0 gets added later on).
>
> Not sure if it's happening because of some incompatibility with Jenkins API, 
> or because of the way that Jenkins plug-ins work. Any idea why the 
> ServiceLoader would not find the JenaSubsystemLifecycle implementations?
>
> Thank youBruno
> ps: two trivial typos fixed in the documentation notes about jena 
> initialization in r1721654 for jena-site
>
>
>        From: Andy Seaborne 
>  To: dev@jena.apache.org
>  Sent: Friday, 25 December 2015 4:00 AM
>  Subject: Re: [jena-jdbc] Need to call ARQ.init() before using TDBDriver
>
> On 24/12/15 11:01, Bruno P. Kinoshita wrote:
>> Hi,
>>
>> I am writing a plug-in for Jenkins to collect metadata about builds and 
>> store in Jena TDB. Then will a SPARQL Endpoint to Jenkins (not sure how yet, 
>> probably will init a Fuseki server within Jenkins).
>>
>> An initial experimentation is to extend the Database Plugin to support 
>> SPARQL. The Database Plugin in Jenkins uses JDBC, so I decided to use 
>> jena-jdbc. However, when validating the connection I'm getting the following 
>> exception (full log in https://gist.github.com/kinow/efec3e14764f9cc002df).
>>
>> Caused by: java.lang.NullPointerException at 
>> org.apache.jena.tdb.sys.SystemTDB.determineFileMode(SystemTDB.java:381) at 
>> org.apache.jena.tdb.sys.SystemTDB.fileMode(SystemTDB.java:356) at 
>> org.apache.jena.tdb.setup.StoreParamsConst.(StoreParamsConst.java:37)
>>  ... 70 more
>>
>> Looks like it depends on a context being initialised in ARQ beforehand. 
>> After adding a call to ARQ.init ([1]) the plug-in worked fine, and I could 
>> validate the connection. But I couldn't find any mention to ARQ.init in the 
>> documentation that I used from jena-jdbc ([2], [3]).
>>
>> I used jena-jdbc in the past with Squirrel SQL, but I believe it 

[jira] [Commented] (JENA-1088) Fuseki 2 allows duplicate datasets when using only spaces in name

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15072268#comment-15072268
 ] 

ASF subversion and git services commented on JENA-1088:
---

Commit c81557a188620988204c8c02e8d05787dffae10c in jena's branch 
refs/heads/master from [~brunodepau...@yahoo.com.br]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=c81557a ]

JENA-1088: trim dataset name before serialize/submitting it


> Fuseki 2 allows duplicate datasets when using only spaces in name
> -
>
> Key: JENA-1088
> URL: https://issues.apache.org/jira/browse/JENA-1088
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Fuseki
>Reporter: Bruno P. Kinoshita
>Assignee: Andy Seaborne
>  Labels: web
> Attachments: JENA-1088.png, Jena-1088-AFS-1.patch
>
>   Original Estimate: 2h
>  Time Spent: 2h
>  Remaining Estimate: 0h
>
> Was testing Fuseki 2, before reviewing the docs, and decided to experiment a 
> few things. Looks like if you use just spaces in the dataset name, you are 
> allowed to create a new one, and it gets the name "/". Which is fine.
> But if you try that again with another random number of spaces, it inserts 
> another dataset with the same name.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JENA-1088) Fuseki 2 allows duplicate datasets when using only spaces in name

[Bruno P. Kinoshita (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15072271#comment-15072271
 ] 

Bruno P. Kinoshita commented on JENA-1088:
--

+1 to close it Andy?

> Fuseki 2 allows duplicate datasets when using only spaces in name
> -
>
> Key: JENA-1088
> URL: https://issues.apache.org/jira/browse/JENA-1088
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Fuseki
>Reporter: Bruno P. Kinoshita
>Assignee: Andy Seaborne
>  Labels: web
> Attachments: JENA-1088.png, Jena-1088-AFS-1.patch
>
>   Original Estimate: 2h
>  Time Spent: 2h
>  Remaining Estimate: 0h
>
> Was testing Fuseki 2, before reviewing the docs, and decided to experiment a 
> few things. Looks like if you use just spaces in the dataset name, you are 
> allowed to create a new one, and it gets the name "/". Which is fine.
> But if you try that again with another random number of spaces, it inserts 
> another dataset with the same name.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JENA-1088) Fuseki 2 allows duplicate datasets when using only spaces in name

[Bruno P. Kinoshita (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15072270#comment-15072270
 ] 

Bruno P. Kinoshita commented on JENA-1088:
--

Added a simple trim in the HTML input field value, just before its value is 
serialized and sent to the server layer.

Adding dataset names with spaces still displays a server error message in a 
bottom panel on the UI, but I think that's fine.

I tried to remove the old datasets, that had several spaces, and the UI didn't 
work (I could delete other datasets like /books, /test). So I think this simple 
validation may prevent some issues from being reported here, but in the future 
we may have to add/modify the rules according to issues/bugs and user reports.

> Fuseki 2 allows duplicate datasets when using only spaces in name
> -
>
> Key: JENA-1088
> URL: https://issues.apache.org/jira/browse/JENA-1088
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Fuseki
>Reporter: Bruno P. Kinoshita
>Assignee: Andy Seaborne
>  Labels: web
> Attachments: JENA-1088.png, Jena-1088-AFS-1.patch
>
>   Original Estimate: 2h
>  Time Spent: 2h
>  Remaining Estimate: 0h
>
> Was testing Fuseki 2, before reviewing the docs, and decided to experiment a 
> few things. Looks like if you use just spaces in the dataset name, you are 
> allowed to create a new one, and it gets the name "/". Which is fine.
> But if you try that again with another random number of spaces, it inserts 
> another dataset with the same name.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (JENA-755) jena-jdbc-driver-tdb uses a lot of disk space on MSWindows.

[Bruno P. Kinoshita (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JENA-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bruno P. Kinoshita reassigned JENA-755:
---

Assignee: Bruno P. Kinoshita

> jena-jdbc-driver-tdb uses a lot of disk space on MSWindows.
> ---
>
> Key: JENA-755
> URL: https://issues.apache.org/jira/browse/JENA-755
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Build
>Affects Versions: Jena 2.12.0
>Reporter: Andy Seaborne
>Assignee: Bruno P. Kinoshita
>
> http://mail-archives.apache.org/mod_mbox/jena-dev/201408.mbox/%3CCAPTxtVOp3aLTGG1Q4qNqnWcLWwvBRw0CRSozrPt_L687obwN1g%40mail.gmail.com%3E
> {quote}
> jena-tdb creates 11.6 GB of test files in "target/tdb-testing/".  There are
> about 100 TDB databases created with most of them weighing in at 192 MB
> each.
> jena-jdbc-driver-tdb creates at least 45 GB of test files in %TEMP%
>  (C:\Users\sallen\AppData\Local\Temp).  There are at least 318 databases
> (192 MB each).  I ran out of disk space at this point (I have a fairly
> small SSD in my laptop), and couldn't actually get it to finish.
> I would think that this is a combination of two issues:
> 1. Sparse files are not used in Windows for the TDB databases (leading to
> the 192 MB databases)
> 2. The JVM bug that does not allow unmapping of memory mapped files until
> the JVM exits means that the unit test databases cannot be deleted at the
> end of each test
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JENA-755) jena-jdbc-driver-tdb uses a lot of disk space on MSWindows.

[Bruno P. Kinoshita (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15072272#comment-15072272
 ] 

Bruno P. Kinoshita commented on JENA-755:
-

Assigning to me temporarily as I have access to a Windows box. I will try to 
reproduce and report it here on the next days.

> jena-jdbc-driver-tdb uses a lot of disk space on MSWindows.
> ---
>
> Key: JENA-755
> URL: https://issues.apache.org/jira/browse/JENA-755
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Build
>Affects Versions: Jena 2.12.0
>Reporter: Andy Seaborne
>Assignee: Bruno P. Kinoshita
>
> http://mail-archives.apache.org/mod_mbox/jena-dev/201408.mbox/%3CCAPTxtVOp3aLTGG1Q4qNqnWcLWwvBRw0CRSozrPt_L687obwN1g%40mail.gmail.com%3E
> {quote}
> jena-tdb creates 11.6 GB of test files in "target/tdb-testing/".  There are
> about 100 TDB databases created with most of them weighing in at 192 MB
> each.
> jena-jdbc-driver-tdb creates at least 45 GB of test files in %TEMP%
>  (C:\Users\sallen\AppData\Local\Temp).  There are at least 318 databases
> (192 MB each).  I ran out of disk space at this point (I have a fairly
> small SSD in my laptop), and couldn't actually get it to finish.
> I would think that this is a combination of two issues:
> 1. Sparse files are not used in Windows for the TDB databases (leading to
> the 192 MB databases)
> 2. The JVM bug that does not allow unmapping of memory mapped files until
> the JVM exits means that the unit test databases cannot be deleted at the
> end of each test
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JENA-1088) Fuseki 2 allows duplicate datasets when using only spaces in name

[Andy Seaborne (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15072275#comment-15072275
 ] 

Andy Seaborne commented on JENA-1088:
-

Yes 

And generally, just resolve things as you see fit.

There needs to be a balance between opening (which is not a high cost to the 
reporter) and resolving to be useful.

We seem to be consolidating around "resolving" then "closing" when the next 
release happens. At least, we did that last couple of times (and I turned off 
the email notification on bulk change for resolved->closed that than 50+ emails 
to the dev@ list :-)

> Fuseki 2 allows duplicate datasets when using only spaces in name
> -
>
> Key: JENA-1088
> URL: https://issues.apache.org/jira/browse/JENA-1088
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Fuseki
>Reporter: Bruno P. Kinoshita
>Assignee: Andy Seaborne
>  Labels: web
> Attachments: JENA-1088.png, Jena-1088-AFS-1.patch
>
>   Original Estimate: 2h
>  Time Spent: 2h
>  Remaining Estimate: 0h
>
> Was testing Fuseki 2, before reviewing the docs, and decided to experiment a 
> few things. Looks like if you use just spaces in the dataset name, you are 
> allowed to create a new one, and it gets the name "/". Which is fine.
> But if you try that again with another random number of spaces, it inserts 
> another dataset with the same name.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JENA-1080) Fuseki Web Interface incompatible with Internet Explorer

[Andy Seaborne (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15072280#comment-15072280
 ] 

Andy Seaborne commented on JENA-1080:
-

From:

https://repository.apache.org/content/repositories/snapshots/org/apache/jena/apache-jena-fuseki/2.4.0-SNAPSHOT/

Build 20 "20151227.223413-20" or later (i.e the bottom of the list, not the 
top).


> 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
>Assignee: Bruno P. Kinoshita
>Priority: Trivial
>  Labels: windows
> Attachments: JENA-1080-001.png, JENA-1080-002.png, JENA-1080-003.png, 
> JENA-1080-004.png
>
>
> 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)

[jira] [Comment Edited] (JENA-1080) Fuseki Web Interface incompatible with Internet Explorer

[Bruno P. Kinoshita (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15072257#comment-15072257
 ] 

Bruno P. Kinoshita edited comment on JENA-1080 at 12/28/15 2:01 AM:


That's great Donald! The change has been committed, so you have a few different 
ways to test it. If you can manually edit the HTML pages (you may have to 
restart Tomcat, or Fuseki) you can add the HTML meta tag missing. Or 
alternatively, you can grab a snapshot built after today (27/Dec/2015 21:49 
UTC), or build from sources. Hope that works, and thanks for testing it.


was (Author: kinow):
That's great Donald! The change has been committed, so you have a few different 
ways to test it. If you can manually edit the HTML pages (you may have to 
restart Tomcat, or Fuseki) you can add the HTML meta tag missing. Or 
alternatively, you can grab a snapshot built after today (28/Dec/2015 21:49 
UTC), or build from sources. Hope that works, and thanks for testing it.

> 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
>Assignee: Bruno P. Kinoshita
>Priority: Trivial
>  Labels: windows
> Attachments: JENA-1080-001.png, JENA-1080-002.png, JENA-1080-003.png, 
> JENA-1080-004.png
>
>
> 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)

[jira] [Resolved] (JENA-1088) Fuseki 2 allows duplicate datasets when using only spaces in name

[Bruno P. Kinoshita (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JENA-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bruno P. Kinoshita resolved JENA-1088.
--
Resolution: Fixed

> Fuseki 2 allows duplicate datasets when using only spaces in name
> -
>
> Key: JENA-1088
> URL: https://issues.apache.org/jira/browse/JENA-1088
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Fuseki
>Reporter: Bruno P. Kinoshita
>Assignee: Andy Seaborne
>  Labels: web
> Attachments: JENA-1088.png, Jena-1088-AFS-1.patch
>
>   Original Estimate: 2h
>  Time Spent: 2h
>  Remaining Estimate: 0h
>
> Was testing Fuseki 2, before reviewing the docs, and decided to experiment a 
> few things. Looks like if you use just spaces in the dataset name, you are 
> allowed to create a new one, and it gets the name "/". Which is fine.
> But if you try that again with another random number of spaces, it inserts 
> another dataset with the same name.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JENA-1088) Fuseki 2 allows duplicate datasets when using only spaces in name

[Bruno P. Kinoshita (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15072330#comment-15072330
 ] 

Bruno P. Kinoshita commented on JENA-1088:
--

Note taken Andy. Will mark issues as resolved first and will let the Closed for 
when someone is cutting a release. Thanks!

> Fuseki 2 allows duplicate datasets when using only spaces in name
> -
>
> Key: JENA-1088
> URL: https://issues.apache.org/jira/browse/JENA-1088
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Fuseki
>Reporter: Bruno P. Kinoshita
>Assignee: Andy Seaborne
>  Labels: web
> Attachments: JENA-1088.png, Jena-1088-AFS-1.patch
>
>   Original Estimate: 2h
>  Time Spent: 2h
>  Remaining Estimate: 0h
>
> Was testing Fuseki 2, before reviewing the docs, and decided to experiment a 
> few things. Looks like if you use just spaces in the dataset name, you are 
> allowed to create a new one, and it gets the name "/". Which is fine.
> But if you try that again with another random number of spaces, it inserts 
> another dataset with the same name.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)