New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

One writable graph per thread/transaction dataset #204

Closed
wants to merge 13 commits into
base: master
from

Conversation

Projects
None yet
3 participants
@ajs6f
Member

ajs6f commented Jan 11, 2017

@afs

This comment has been minimized.

Show comment
Hide comment
@afs

afs Jan 11, 2017

Member

Immediate reaction: Why are the tests in "pergraph"?

If this is the beginning of "jena-ldp", do we want a package under src/main?

Member

afs commented Jan 11, 2017

Immediate reaction: Why are the tests in "pergraph"?

If this is the beginning of "jena-ldp", do we want a package under src/main?

@ajs6f

This comment has been minimized.

Show comment
Hide comment
@ajs6f

ajs6f Jan 11, 2017

Member

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 PR is exactly that-- is this useful only for LDP-type workloads (in which case maybe it belongs outside ARQ entirely) or not (in which case it has more claim to be in ARQ)?

Member

ajs6f commented Jan 11, 2017

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 PR is exactly that-- is this useful only for LDP-type workloads (in which case maybe it belongs outside ARQ entirely) or not (in which case it has more claim to be in ARQ)?

@asfbot

This comment has been minimized.

Show comment
Hide comment
@asfbot

asfbot Jan 11, 2017

Claude Warren on dev@jena.apache.org replies:
perhaps in extras?

asfbot commented Jan 11, 2017

Claude Warren on dev@jena.apache.org replies:
perhaps in extras?

@asfbot

This comment has been minimized.

Show comment
Hide comment
@asfbot

asfbot Jan 11, 2017

"A. Soroka" on dev@jena.apache.org replies:
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?=20

The other direction here is forward with respect to locking. Claude and =
others (including me) have thrown around ideas on the list about how we =
could introduce more finely-grained locking for datasets, and I =
definitely think of this as a first tiny baby step in that direction.


A. Soroka
The University of Virginia Library
I
is
case
more
have your
feature
please
ticket

asfbot commented Jan 11, 2017

"A. Soroka" on dev@jena.apache.org replies:
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?=20

The other direction here is forward with respect to locking. Claude and =
others (including me) have thrown around ideas on the list about how we =
could introduce more finely-grained locking for datasets, and I =
definitely think of this as a first tiny baby step in that direction.


A. Soroka
The University of Virginia Library
I
is
case
more
have your
feature
please
ticket

@asfbot

This comment has been minimized.

Show comment
Hide comment
@asfbot

asfbot Jan 13, 2017

Andy Seaborne on dev@jena.apache.org replies:
+1 to extras.

I think that has a lot of merit for small things to be in extras. It is
easier to point at and say "new - subject to change".

As does separate github repos - especiallty where the early status is
unstable, where access while being developed for a the most intersted
people is not affected by Jena release cycles.

that-- is this useful only for LDP-type workloads (in which case maybe
it belongs outside ARQ entirely) or not (in which case it has more
claim to be in ARQ)?

How about describing some use case where you think it might be helpful?

Just having something in the codebase does not really ask the question
you have about what might be - code tends to ask "does this exact thing
do ..."

 Andy

asfbot commented Jan 13, 2017

Andy Seaborne on dev@jena.apache.org replies:
+1 to extras.

I think that has a lot of merit for small things to be in extras. It is
easier to point at and say "new - subject to change".

As does separate github repos - especiallty where the early status is
unstable, where access while being developed for a the most intersted
people is not affected by Jena release cycles.

that-- is this useful only for LDP-type workloads (in which case maybe
it belongs outside ARQ entirely) or not (in which case it has more
claim to be in ARQ)?

How about describing some use case where you think it might be helpful?

Just having something in the codebase does not really ask the question
you have about what might be - code tends to ask "does this exact thing
do ..."

 Andy
@ajs6f

This comment has been minimized.

Show comment
Hide comment
@ajs6f

ajs6f Jan 13, 2017

Member

That's a really fair point about providing some use cases. An example that occurs to me is RDF-based persistence where Java entities are being saved into a dataset. I think @Claudenw has something like that going on in PA4RDF. This kind of dataset could act as a simple but powerful cache for that kind of system.

Member

ajs6f commented Jan 13, 2017

That's a really fair point about providing some use cases. An example that occurs to me is RDF-based persistence where Java entities are being saved into a dataset. I think @Claudenw has something like that going on in PA4RDF. This kind of dataset could act as a simple but powerful cache for that kind of system.

@ajs6f

This comment has been minimized.

Show comment
Hide comment
@ajs6f

ajs6f Jan 13, 2017

Member

I will retarget this at jena-extras. It does make more sense.

Member

ajs6f commented Jan 13, 2017

I will retarget this at jena-extras. It does make more sense.

@ajs6f

This comment has been minimized.

Show comment
Hide comment
@ajs6f

ajs6f Jan 16, 2017

Member

It looks like in order to put this in jena-extras, I will need to create a new modules there. Any opinions about the name? Maybe jena-optional-datasets or something like that?

Member

ajs6f commented Jan 16, 2017

It looks like in order to put this in jena-extras, I will need to create a new modules there. Any opinions about the name? Maybe jena-optional-datasets or something like that?

@afs

This comment has been minimized.

Show comment
Hide comment
@afs

afs Jan 17, 2017

Member

Possible naming approaches:

  1. "Small things" being curated go into a general jena-extras/jena-wip/jena-labs/jena-optional module with the idea that that is just while they mature, Downside: things go into that module and don't progress.
  2. At the other end of the spectrum, this is a step for jena-ldp so to get attention on that, use that name. Downside: over selling.
  3. Specific for this one thing: jena-writer-dsg, a name for the write-centric dataset. Downside: does not connect to LDP usage.
Member

afs commented Jan 17, 2017

Possible naming approaches:

  1. "Small things" being curated go into a general jena-extras/jena-wip/jena-labs/jena-optional module with the idea that that is just while they mature, Downside: things go into that module and don't progress.
  2. At the other end of the spectrum, this is a step for jena-ldp so to get attention on that, use that name. Downside: over selling.
  3. Specific for this one thing: jena-writer-dsg, a name for the write-centric dataset. Downside: does not connect to LDP usage.
@ajs6f

This comment has been minimized.

Show comment
Hide comment
@ajs6f

ajs6f Jan 17, 2017

Member

Yeah, judging by the general silence in response to my question about "Does anyone have other use cases for this kind of thing?" I'm not going to push on that I'm happy for it to be helpful to the LDP use case. But I don't want to oversell that either. I don't know that Jena would want to house an LDP impl or that I would want to do that here. Hm. Well, one question is whether we think that there ever would be a full-on jena-ldp?

Member

ajs6f commented Jan 17, 2017

Yeah, judging by the general silence in response to my question about "Does anyone have other use cases for this kind of thing?" I'm not going to push on that I'm happy for it to be helpful to the LDP use case. But I don't want to oversell that either. I don't know that Jena would want to house an LDP impl or that I would want to do that here. Hm. Well, one question is whether we think that there ever would be a full-on jena-ldp?

@ajs6f

This comment has been minimized.

Show comment
Hide comment
@ajs6f

ajs6f Jan 22, 2017

Member

I'm starting to wonder whether I should back up here and just go for the more general 2-phase-locking design as @afs discusses in the Jira ticket, or even to try to generalize to more amorphous locking regions. Doing those things would open up more use cases which might make this stuff viable for jena-arq itself.

Member

ajs6f commented Jan 22, 2017

I'm starting to wonder whether I should back up here and just go for the more general 2-phase-locking design as @afs discusses in the Jira ticket, or even to try to generalize to more amorphous locking regions. Doing those things would open up more use cases which might make this stuff viable for jena-arq itself.

@ajs6f

This comment has been minimized.

Show comment
Hide comment
@ajs6f

ajs6f Feb 16, 2017

Member

Closing in favor of further more general discussion about points raised on this PR.

Member

ajs6f commented Feb 16, 2017

Closing in favor of further more general discussion about points raised on this PR.

@ajs6f ajs6f closed this Feb 16, 2017

@asfgit asfgit deleted the ThreadPerGraphDataset branch Feb 20, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment