[
https://issues.apache.org/jira/browse/RYA-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15951421#comment-15951421
]
ASF GitHub Bot commented on RYA-266:
------------------------------------
GitHub user DLotts opened a pull request:
https://github.com/apache/incubator-rya/pull/149
RYA-266 Added calls to init() where-ever the Accumulo temporal indexer is
used for storing
## Description
The dao manages multitable batch writer, but that was not being used, so
writers might never be flushed.
### Tests
Repaired tests. No new tests.
### Links
[Jira](https://issues.apache.org/jira/browse/RYA-266)
### Checklist
- [ ] Code Review
#### People To Reivew
People that know indexing, or know RyaOutputFormatTest
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/DLotts/incubator-rya RYA-266_tempo_flush
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-rya/pull/149.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #149
----
commit 72925fe26719c7c006aced94ba975d959655d008
Author: David W. Lotts <[email protected]>
Date: 2017-03-31T18:05:07Z
RYA-266 Added init() and other calls where ever the Accumulo temporal
indexer is created and used for storing.
----
> Temporal index fails to write when using non-mock accumulo
> ----------------------------------------------------------
>
> Key: RYA-266
> URL: https://issues.apache.org/jira/browse/RYA-266
> Project: Rya
> Issue Type: Sub-task
> Components: dao, sail
> Environment: indexing
> Reporter: David W. Lotts
> Assignee: David W. Lotts
> Priority: Blocker
> Labels: flush, index, temporal
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Temporal indexing writes nothing to it's table name: [prefix]temporal.
> It does seem to work for a mock instance. It might also work for a large
> ingest since it would force a flush.
> See the parent RYA-72 for an explanation.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
