[
https://issues.apache.org/jira/browse/JENA-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14605364#comment-14605364
]
ASF GitHub Bot commented on JENA-979:
-
Github user afs commented on the pull request:
Github user ajs6f commented on a diff in the pull request:
https://github.com/apache/jena/pull/82#discussion_r33451617
--- Diff:
jena-fuseki2/jena-fuseki-core/src/main/java/org/apache/jena/fuseki/mgt/ActionBackupList.java
---
@@ -0,0 +1,98 @@
+/**
+ * Licensed to the
Github user afs commented on the pull request:
https://github.com/apache/jena/pull/82#issuecomment-116601250
Indeed - etags are one example of a server driven mechanism. They need more
machinery than this PR has though. HTTP headers are not always easy to deal
with in client
[
https://issues.apache.org/jira/browse/JENA-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14605415#comment-14605415
]
ASF GitHub Bot commented on JENA-979:
-
Github user afs commented on the pull request:
A quick discussion of ETags in the backup admin PR that was sent by Yang
Yuanzhe led me to this issue:
https://issues.apache.org/jira/browse/JENA-388
for Make Fuseki responses cacheable and which has been around for a little
while. I was wondering about a couple of potential approaches here
[
https://issues.apache.org/jira/browse/JENA-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14605596#comment-14605596
]
A. Soroka commented on JENA-388:
I don't see {{DatasetRef}} any more in Fuseki 2. Is that
If there were an ETag per dataset and a method on the dataset to force an
ETag reset would this address the index issue in that the indexer could
reset the ETag when it deemed appropriate?
In any case I would go with the first choice.
Is there anything that prohibits sending both an ETag and a
On Jun 29, 2015, at 9:33 AM, Claude Warren cla...@xenei.com wrote:
If there were an ETag per dataset and a method on the dataset to force an
ETag reset would this address the index issue in that the indexer could reset
the ETag when it deemed appropriate?
It might-- for that indexer. I would
GitHub user ajs6f opened a pull request:
https://github.com/apache/jena/pull/83
Removing out-of-date comment and empty @Overrides from Dataset
A comment in `Dataset` indicated that it did not implement `Transactional`
when in fact it now does. I removed that comment and the
[
https://issues.apache.org/jira/browse/JENA-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14605421#comment-14605421
]
ASF GitHub Bot commented on JENA-979:
-
Github user ajs6f commented on the pull request:
[
https://issues.apache.org/jira/browse/JENA-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14605469#comment-14605469
]
ASF GitHub Bot commented on JENA-979:
-
Github user ajs6f commented on the pull request:
Github user ajs6f commented on a diff in the pull request:
https://github.com/apache/jena/pull/82#discussion_r33457733
--- Diff:
jena-fuseki2/jena-fuseki-core/src/main/java/org/apache/jena/fuseki/mgt/ActionBackupList.java
---
@@ -0,0 +1,98 @@
+/**
+ * Licensed to the
Github user yyz1989 commented on the pull request:
https://github.com/apache/jena/pull/82#issuecomment-116636657
Yeah, I agree with Rob and Andy. I do think accepting POST is necessary,
but I apologize for my negligence for HEAD. That is due to my laziness because
I took the main
[
https://issues.apache.org/jira/browse/JENA-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14605542#comment-14605542
]
ASF GitHub Bot commented on JENA-979:
-
Github user yyz1989 commented on the pull
Github user afs commented on the pull request:
https://github.com/apache/jena/pull/82#issuecomment-116589395
I disagree a bit about POST - yes, it's not nice REST but it is
pragmatically useful to ensure up-to-date information (the client can force it
even if the server or proxies
[
https://issues.apache.org/jira/browse/JENA-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14605363#comment-14605363
]
ASF GitHub Bot commented on JENA-979:
-
Github user afs commented on the pull request:
Github user ajs6f commented on the pull request:
https://github.com/apache/jena/pull/82#issuecomment-116597497
`POST` is one way to enable a force up-to-date`, but it should also be
possible to supply an ETag, which is a little more to the exact need. Perhaps
Fuseki has helpers for
[
https://issues.apache.org/jira/browse/JENA-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14605407#comment-14605407
]
ASF GitHub Bot commented on JENA-979:
-
Github user ajs6f commented on the pull request:
Github user ajs6f commented on the pull request:
https://github.com/apache/jena/pull/82#issuecomment-116603288
Okay-- do you think it's worth a separate ticket and PR for some helpers
for ETags, so that future new Fuseki HTTP functions could offer them at low
cost?
---
If your
[
https://issues.apache.org/jira/browse/JENA-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14605515#comment-14605515
]
ASF GitHub Bot commented on JENA-979:
-
Github user ajs6f commented on the pull request:
[
https://issues.apache.org/jira/browse/JENA-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14605513#comment-14605513
]
ASF GitHub Bot commented on JENA-979:
-
Github user afs commented on the pull request:
Github user ajs6f commented on the pull request:
https://github.com/apache/jena/pull/82#issuecomment-116628538
Okay, sorry to cloud the waters.
---
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
Github user afs commented on the pull request:
https://github.com/apache/jena/pull/82#issuecomment-116609093
Here, the client browser is an admin interface.The read-information
operations are not a performance pain-point.
Helpers presume how they are being used in Fuseki is
Github user afs commented on the pull request:
https://github.com/apache/jena/pull/82#issuecomment-116628492
We are agreed that it's not related to this PR. Let's discuss it on dev@
and not tangle this PR with that discussion.
---
If your project is set up for it, you can reply to
[
https://issues.apache.org/jira/browse/JENA-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14605536#comment-14605536
]
ASF GitHub Bot commented on JENA-979:
-
Github user ajs6f commented on a diff in the pull
[
https://issues.apache.org/jira/browse/JENA-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14605402#comment-14605402
]
ASF GitHub Bot commented on JENA-979:
-
Github user ajs6f commented on a diff in the pull
[
https://issues.apache.org/jira/browse/JENA-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14605530#comment-14605530
]
ASF GitHub Bot commented on JENA-979:
-
Github user yyz1989 commented on a diff in the
Github user yyz1989 commented on a diff in the pull request:
https://github.com/apache/jena/pull/82#discussion_r33457422
--- Diff:
jena-fuseki2/jena-fuseki-core/src/main/java/org/apache/jena/fuseki/mgt/ActionBackupList.java
---
@@ -0,0 +1,98 @@
+/**
+ * Licensed to the
I am not familure with how the indexing interplays with the rest of the
Jena system. My assumption is, like you, that we only want the ETag in the
Fuseki layer. However, to generate an ETag it seems like Fuseki will need
to be able to ask the underlying dataset when the last change occured, but
On 29/06/15 09:57, Claude Warren wrote:
The contract-test-maven-plugin should be version 0.1.4
Maven disagrees with you :-)
That's the job output so something is wrong in the setup ...
jena-parent : nothing in the pluginManagemen section but there is a
dependency (which should not be in
I'll have to mess with the build when I get home.
As for the iteraor solution --- I am not at all certain why there was a
problem. It sounded like the generic solution was starting the process too
soon. But I didn't really follow. I'll look tonight and see if I can
follow your logic.
Claude
I can only speak for the use cases I actually know about. ETags would get used,
because the most important web app in my concern that is potentially a client
to Fuseki would be able to use them. But that is just one case.
JENA-626 would be great in any regard.
---
A. Soroka
The University of
Good point. (Speaking as someone who regularly has to be corrected about this
{grin}.)
---
A. Soroka
The University of Virginia Library
On Jun 29, 2015, at 12:57 PM, Andy Seaborne a...@apache.org wrote:
Good comments - I've made some revisions to the page based on this input.
It reminded
On 29/06/15 17:05, Claude Warren wrote:
I'll have to mess with the build when I get home.
As for the iteraor solution --- I am not at all certain why there was a
problem.
It sounded like the generic solution was starting the process too
soon. But I didn't really follow. I'll look tonight
Good comments - I've made some revisions to the page based on this input.
It reminded me to add a request for pull requests to have commits
focused on the pull requests/contribution functionality, not details of
how the code has evolved up to that point (i.e the internal history).
Different
[
https://issues.apache.org/jira/browse/JENA-977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14605844#comment-14605844
]
ASF subversion and git services commented on JENA-977:
--
Commit
For completeness:
A 3rd option is injecting a VALUEs at the start of the query:
SELECT ?x
WHERE
{ ?s :p ?x
FILTER ( ?x 57 )
}
and ?x = :X
PREFIX : http://example/
SELECT ?x
WHERE
{ VALUES ?x { :X }
?s :p ?x
FILTER ( ?x 57 )
}
Like PQ, it's
There is no case of external modification of the database which Fuseki
is running. A disaster will occur otherwise. [Modifying externally
while running requires a different approach (e.g. switching between two
copies of the database ... maybe ... so many ways to corrupt a database
... ).]
[
https://issues.apache.org/jira/browse/JENA-923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-923.
Resolution: Done
Fix Version/s: Jena 3.0.0
Populate jena-base
--
[
https://issues.apache.org/jira/browse/JENA-782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne reopened JENA-782:
reopen to correct version
Provide configurability of TDB in database setup
[
https://issues.apache.org/jira/browse/JENA-782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-782:
---
Fix Version/s: (was: Jena 2.13.0)
Jena 3.0.0
Provide configurability of TDB in
[
https://issues.apache.org/jira/browse/JENA-782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne closed JENA-782.
--
Resolution: Fixed
Provide configurability of TDB in database setup
[
https://issues.apache.org/jira/browse/JENA-973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne closed JENA-973.
--
Resolution: Fixed
Fix Version/s: Jena 3.0.0
Expression NOT EXISTS define equality by alegbra
Github user ajs6f commented on the pull request:
https://github.com/apache/jena/pull/82#issuecomment-116612135
I meant something as simple as a method that accepts an identifier and
response and adds the correctly-formatted tag.
---
If your project is set up for it, you can reply to
Looking at your changes they make perfect sense to me.
On Mon, Jun 29, 2015 at 5:31 PM, Andy Seaborne a...@apache.org wrote:
On 29/06/15 17:05, Claude Warren wrote:
I'll have to mess with the build when I get home.
As for the iteraor solution --- I am not at all certain why there was a
The contract-test-maven-plugin should be version 0.1.4
[INFO] --- contract-test-maven-plugin:0.1.2:contract-test (default) @
jena-core ---
On Mon, Jun 29, 2015 at 9:50 AM, Apache Jenkins Server
jenk...@builds.apache.org wrote:
See
Github user rvesse commented on the pull request:
https://github.com/apache/jena/pull/82#issuecomment-116555847
+1 to the idea
The implementation seems to violate REST principles though
`POST` should be used for changing data so should not be supported for a
service
[
https://issues.apache.org/jira/browse/JENA-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14605333#comment-14605333
]
ASF GitHub Bot commented on JENA-979:
-
Github user rvesse commented on the pull request:
48 matches
Mail list logo
