Just to say. Everything is "ok". You can publish when you can!
Very Thanks and Very Happy to contribute!
2013/1/19 Guilherme Jose Carvalho Cavalcanti
> I checked e fixed some mistakes. Till now, everything is OK for both
> tutorials that I submitted.
>
> I'm waiting for the other two tutorial
[
https://issues.apache.org/jira/browse/JENA-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13571770#comment-13571770
]
Elli Schwarz commented on JENA-164:
---
Is any further work planned on this issue? I use Fuse
So UpdateAction, UpdateExecutionFactory, UpdateProcessor,
UpdateProcessorStreaming are part of the user API and should not have
changed much. They are the way to interact with the update system.
For storage engine implementers, what has changed is that UpdateEngine
is now stream based. If, as a s
Thanks for doing the refactor, I never did find time for that last week
Rob
On 2/5/13 11:14 AM, "a...@apache.org" wrote:
>Author: andy
>Date: Tue Feb 5 11:14:13 2013
>New Revision: 1442540
>
>URL: http://svn.apache.org/viewvc?rev=1442540&view=rev
>Log:
>Prepare for overridable local name rul
Actually part of my email was still valid, UpdateAction.execute() would
not have fallen back to non-streaming, should now do this as of my latest
commit
Rob
On 2/5/13 9:19 AM, "Rob Vesse" wrote:
>Ignore my last email, having problems with Eclipse auto-complete and
>workspace versioning sync is
Ignore my last email, having problems with Eclipse auto-complete and
workspace versioning sync issues, also my jet lagged brain having flown
back into the US only yesterday ;)
Garghhh
Rob
On 2/5/13 9:16 AM, "Rob Vesse" wrote:
>Ok I am slightly stumped by the latest changes
>
>UpdateAction.exe
Ok I am slightly stumped by the latest changes
UpdateAction.execute() is broken in that it only tries to do streaming
updates and can't fall back to non-streaming.
UpdateProcessor no longer has any execute() method so is the assumption
simply that the update happens when startRequest() is called
I don't think we have a document on that anywhere, I assume here you are
talking about open/unassigned JIRAs possibly with patch(es) attached?
Generally speaking if it's unassigned on JIRA feel free to take it and
start looking at it, if someone is assigned but there's no apparent
activity you can
I have unified the two update paths into a single path. I also
removed the ability to pass in an UpdateRequest into the
UpdateEngineFactory. In fact, I've eliminated all the places you
could pass one in. Since with the streaming capability, we won't be
able to have one. This required one chang
On 01/02/13 21:06, Stephen Allen wrote:
Replying to both Andy and Rob in this email, comments inline.
...
Initial binding looks like a mistake because an update is multiple
operations and historical at best. Remove this (via a deprecation cycle?).
Use BIND or VALUES nowadays.
Agreed. Initi
10 matches
Mail list logo
