[
https://issues.apache.org/jira/browse/JENA-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-1037:
Comment: was deleted
(was: Commit 60cdb4ab2bc150c41fd18f16750fc5d8efaadd04 in jena's branch
On Thu, Nov 12, 2015 at 12:55 PM, Rob Vesse wrote:
> Comments inline:
>
> On 12/11/2015 06:31, "Andy Seaborne" wrote:
>
> >On 12/11/15 00:42, Rob Vesse wrote:
> >> Andy
> >>
> >> I was talking to some folks at a major bank the other day about TDB and
>
Github user ajs6f commented on the pull request:
https://github.com/apache/jena/pull/94#issuecomment-156126355
@afs Squashed 'em pretty flat. The first commit is journaling operation,
the second is the new in-memory design.
I will wait to hear from you, otherwise moving on
On 12/11/15 00:42, Rob Vesse wrote:
Andy
I was talking to some folks at a major bank the other day about TDB and got
an interesting question that I didn't have an answer to. Essentially they
were interested in learning how you would provide replication and hot-standy
with TDB
For current
[
https://issues.apache.org/jira/browse/JENA-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15002181#comment-15002181
]
ASF GitHub Bot commented on JENA-624:
-
Github user ajs6f commented on the pull request:
[
https://issues.apache.org/jira/browse/JENA-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15002246#comment-15002246
]
ASF GitHub Bot commented on JENA-624:
-
Github user afs commented on the pull request:
[
https://issues.apache.org/jira/browse/JENA-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15002299#comment-15002299
]
ASF GitHub Bot commented on JENA-624:
-
Github user afs commented on the pull request:
[
https://issues.apache.org/jira/browse/JENA-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1500#comment-1500
]
ASF GitHub Bot commented on JENA-624:
-
Github user ajs6f commented on the pull request:
[
https://issues.apache.org/jira/browse/JENA-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15002287#comment-15002287
]
ASF GitHub Bot commented on JENA-624:
-
Github user ajs6f commented on the pull request:
Github user afs commented on the pull request:
https://github.com/apache/jena/pull/94#issuecomment-156148758
It is not the code - it's the way tests are found.
This is what seems to be happening - when running the JUnit tests on the
package (at least in Eclipse and I believe
[
https://issues.apache.org/jira/browse/JENA-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15002210#comment-15002210
]
ASF GitHub Bot commented on JENA-624:
-
Github user afs commented on the pull request:
Github user afs commented on the pull request:
https://github.com/apache/jena/pull/94#issuecomment-156132377
Great.
You don't need `/testing`. The material under there is for testing query
execution, not the dataset storage.
For functional tests,
[
https://issues.apache.org/jira/browse/JENA-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15002214#comment-15002214
]
ASF GitHub Bot commented on JENA-624:
-
Github user ajs6f commented on the pull request:
[
https://issues.apache.org/jira/browse/JENA-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15002220#comment-15002220
]
ASF GitHub Bot commented on JENA-624:
-
Github user afs commented on the pull request:
Github user afs commented on the pull request:
https://github.com/apache/jena/pull/94#issuecomment-156135092
and `AbstractTestTransaction`. Think that's it.
---
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
Github user ajs6f commented on the pull request:
https://github.com/apache/jena/pull/94#issuecomment-156146622
It occurs to me that a better way to explain myself is:
`TestDatasetGraphInMemory` looks the way it does (lots of nested classes)
because I wanted to keep the usual
Github user afs commented on the pull request:
https://github.com/apache/jena/pull/94#issuecomment-156140079
All this can be refined post merge. I've been checking that the existing
test hierarchies run as well.
`TestDatasetGraphInMemory` and `TestInMemory` seem to both call
Comments inline:
On 12/11/2015 06:31, "Andy Seaborne" wrote:
>On 12/11/15 00:42, Rob Vesse wrote:
>> Andy
>>
>> I was talking to some folks at a major bank the other day about TDB and
>>got
>> an interesting question that I didn't have an answer to. Essentially
>>they
>> were
Github user ajs6f commented on the pull request:
https://github.com/apache/jena/pull/94#issuecomment-156149841
Ah, I didn't realize that we were using the automatic
"execute-by-naming-convention" test running as well as the explicit style of
gathering things up into suites.
I'll
[
https://issues.apache.org/jira/browse/JENA-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15002305#comment-15002305
]
ASF GitHub Bot commented on JENA-624:
-
Github user ajs6f commented on the pull request:
20 matches
Mail list logo