Github user ajs6f commented on a diff in the pull request:
https://github.com/apache/jena/pull/202#discussion_r95585136
--- Diff:
jena-base/src/main/java/org/apache/jena/atlas/lib/CollectionUtils.java ---
@@ -22,12 +22,7 @@
public class CollectionUtils
{
-
Github user afs commented on a diff in the pull request:
https://github.com/apache/jena/pull/202#discussion_r95606345
--- Diff:
jena-base/src/main/java/org/apache/jena/atlas/lib/CollectionUtils.java ---
@@ -22,12 +22,7 @@
public class CollectionUtils
{
-
[
https://issues.apache.org/jira/browse/JENA-1230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15818443#comment-15818443
]
A. Soroka commented on JENA-1230:
-
Okay, I'll take a look at the Scala and put on my translating hat.
>
Github user ajs6f commented on a diff in the pull request:
https://github.com/apache/jena/pull/202#discussion_r95584988
--- Diff:
jena-arq/src/main/java/org/apache/jena/sparql/algebra/OpVisitor.java ---
@@ -23,53 +23,53 @@
public interface OpVisitor
{
// Op0
[
https://issues.apache.org/jira/browse/JENA-1230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15819187#comment-15819187
]
A. Soroka commented on JENA-1230:
-
[~sperber], where did you get the type
Github user ajs6f commented on the issue:
https://github.com/apache/jena/pull/203
@afs I think the point that @stain and I are making is that there is no
need for an external resource linkage at all.
---
If your project is set up for it, you can reply to this email and have your
To be honest, I was thinking that if the graph notification for the
cassandra graph needed to notify all the attached graph implementations of
changes I would use Kafka or other similar pluggable Queue to do the
notification.
Claude
On Wed, Jan 11, 2017 at 2:48 PM, A. Soroka
Github user ajs6f commented on a diff in the pull request:
https://github.com/apache/jena/pull/202#discussion_r95613311
--- Diff:
jena-base/src/main/java/org/apache/jena/atlas/lib/CollectionUtils.java ---
@@ -22,12 +22,7 @@
public class CollectionUtils
{
-
GitHub user ajs6f opened a pull request:
https://github.com/apache/jena/pull/204
One writable graph per thread/transaction dataset
A pass at:
https://issues.apache.org/jira/browse/JENA-1274
You can merge this pull request into a Git repository by running:
$ git pull
Hi Claude,
On 09/01/17 19:22, Claude Warren wrote:
Greetings,
Given that the Cassandra server can host multiple client and those
clients can open the same graph on the server simultaneously. Basically
two updatable synchronized views on one data set.
Assume graph A is opened on client X
[
https://issues.apache.org/jira/browse/JENA-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Vesse updated JENA-644:
---
Assignee: (was: Rob Vesse)
> Jena Text documentation needs better examples
>
[
https://issues.apache.org/jira/browse/JENA-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Vesse updated JENA-648:
---
Assignee: (was: Rob Vesse)
> Make TDB datasets harder to corrupt
> ---
>
>
[
https://issues.apache.org/jira/browse/JENA-893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Vesse updated JENA-893:
---
Assignee: (was: Rob Vesse)
> Elephas IO should split BZip2 inputs
>
>
Cassandra does not support transactions. However, I can see the use for a
bounding construct that indicates "all these triples were added/deleted."
The original driver for the Cassandra implementation was that we needed one
for a use case at work. However, Cassandra is generally about speed of
[
https://issues.apache.org/jira/browse/JENA-1230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15818163#comment-15818163
]
Andy Seaborne commented on JENA-1230:
-
A java one would be good. (java because the majority of users
Rob Vesse created JENA-1275:
---
Summary: TransformScopeRename does the wrong thing with FILTER NOT
EXISTS
Key: JENA-1275
URL: https://issues.apache.org/jira/browse/JENA-1275
Project: Apache Jena
Github user stain commented on the issue:
https://github.com/apache/jena/pull/203
For unit tests you can use a JAR-cached context by using the
[jarcache.json](https://github.com/jsonld-java/jsonld-java#loading-contexts-from-classpathjar)
approach and put it together with the JSON
Github user afs commented on the issue:
https://github.com/apache/jena/pull/203
External linkages in the tests is, in the long term, not good. At some
point, the remote resource will be uncontactable. Sometimes people need to run
the test offline as well. So for the long term
Github user afs commented on a diff in the pull request:
https://github.com/apache/jena/pull/202#discussion_r95557264
--- Diff:
jena-arq/src/main/java/org/apache/jena/sparql/algebra/OpVisitor.java ---
@@ -23,53 +23,53 @@
public interface OpVisitor
{
// Op0
-
Github user afs commented on a diff in the pull request:
https://github.com/apache/jena/pull/202#discussion_r95558509
--- Diff:
jena-base/src/main/java/org/apache/jena/atlas/lib/CollectionUtils.java ---
@@ -22,12 +22,7 @@
public class CollectionUtils
{
-
Github user afs commented on the issue:
https://github.com/apache/jena/pull/204
Immediate reaction: Why are the tests in "pergraph"?
If this is the beginning of "jena-ldp", do we want a package under src/main?
---
If your project is set up for it, you can reply to this
Github user ajs6f commented on the issue:
https://github.com/apache/jena/pull/204
`pergraph`: Just thought that `core` was getting awfully crowded. I don't
care one way or the other-- happy to put them anywhere.
`jena-ldp`: One of the questions I'm trying to raise with this
Github user afs commented on the issue:
https://github.com/apache/jena/pull/202
Modified but is generated:
JSON_Parser, SPARQLParser10, SPARQLParser11, SSE_ParserCore
OpVisitorBase is modified.
Various uses of "disjoint" have had the static import removed.
Sure, that would be natural. Let me put the question this way: is a per-graph
arrangement of this kind interesting to anyone who isn't interested in LDP?
The other direction here is forward with respect to locking. Claude and others
(including me) have thrown around ideas on the list about how
Github user ajs6f commented on the issue:
https://github.com/apache/jena/pull/202
Fixed (reverted) the additional autogen files.
---
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
[
https://issues.apache.org/jira/browse/JENA-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15818898#comment-15818898
]
ASF GitHub Bot commented on JENA-1274:
--
GitHub user ajs6f opened a pull request:
[
https://issues.apache.org/jira/browse/JENA-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
François-Paul Servant updated JENA-1276:
Description:
getting org.apache.jena.riot.RiotException: loading remote context
Github user fpservant commented on the issue:
https://github.com/apache/jena/pull/203
Hi,
there are very different points in the discussion, all around one test that
attempts to connect to an external resource.
1) It must first be noted that the test in question
François-Paul Servant created JENA-1276:
---
Summary: "loading remote context failed" reading JSON-LD
Key: JENA-1276
URL: https://issues.apache.org/jira/browse/JENA-1276
Project: Apache Jena
perhaps in extras?
On Wed, Jan 11, 2017 at 7:39 PM, ajs6f wrote:
> Github user ajs6f commented on the issue:
>
> https://github.com/apache/jena/pull/204
>
> `pergraph`: Just thought that `core` was getting awfully crowded. I
> don't care one way or the other-- happy
[
https://issues.apache.org/jira/browse/JENA-1230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A. Soroka reassigned JENA-1230:
---
Assignee: A. Soroka
> Proxy authentication via NTLM does not work
>
31 matches
Mail list logo