Store required data statistics for discovering what adapters are in each index #660
Labels
Milestone
Comments
|
actually the method that would likely be used more often than not is getIndices(ByteArrayId adapterId) or something like a |
|
Should apply this in the delete case as 'check' do not want to have the case where a feature is deleted in one index and not another. |
rwgdrummer
added a commit
that referenced
this issue
Mar 19, 2016
…. Retain the index/adapter assocation to identify possibile indices to query for a given adapter and to enfore a consistent set of indices to write for a given adapter across multiple ingest runs or WFS-T transactions. Lastly, eliminate the redudant visibility constraint when creating an index writer. GEOWAVE-669: moved geowavedemoapp to exmaples so that it could use adapter dependencies; demo app works in windows now
rwgdrummer
added a commit
that referenced
this issue
Mar 22, 2016
# The first commit's message is: Issue #659, #658, #660. Allow the index writer to to multiple indices. Retain the index/adapter assocation to identify possibile indices to query for a given adapter and to enfore a consistent set of indices to write for a given adapter across multiple ingest runs or WFS-T transactions. Lastly, eliminate the redudant visibility constraint when creating an index writer # This is the 2nd commit message: wip # This is the 3rd commit message: wip
rwgdrummer
pushed a commit
that referenced
this issue
Mar 22, 2016
…. Retain the index/adapter assocation to identify possibile indices to query for a given adapter and to enfore a consistent set of indices to write for a given adapter across multiple ingest runs or WFS-T transactions. Lastly, eliminate the redudant visibility constraint when creating an index writer wip wip wip
rwgdrummer
pushed a commit
that referenced
this issue
Mar 22, 2016
…. Retain the index/adapter assocation to identify possibile indices to query for a given adapter and to enfore a consistent set of indices to write for a given adapter across multiple ingest runs or WFS-T transactions. Lastly, eliminate the redudant visibility constraint when creating an index writer wip wip wip wip
rwgdrummer
pushed a commit
that referenced
this issue
Mar 22, 2016
…. Retain the index/adapter assocation to identify possibile indices to query for a given adapter and to enfore a consistent set of indices to write for a given adapter across multiple ingest runs or WFS-T transactions. Lastly, eliminate the redudant visibility constraint when creating an index writer wip wip wip wip wip
rwgdrummer
pushed a commit
that referenced
this issue
Mar 22, 2016
…. Retain the index/adapter assocation to identify possibile indices to query for a given adapter and to enfore a consistent set of indices to write for a given adapter across multiple ingest runs or WFS-T transactions. Lastly, eliminate the redudant visibility constraint when creating an index writer wip wip wip wip wip wip
rwgdrummer
pushed a commit
that referenced
this issue
Mar 22, 2016
…. Retain the index/adapter assocation to identify possibile indices to query for a given adapter and to enfore a consistent set of indices to write for a given adapter across multiple ingest runs or WFS-T transactions. Lastly, eliminate the redudant visibility constraint when creating an index writer wip wip wip wip wip wip wip
rwgdrummer
pushed a commit
that referenced
this issue
Mar 22, 2016
…. Retain the index/adapter assocation to identify possibile indices to query for a given adapter and to enfore a consistent set of indices to write for a given adapter across multiple ingest runs or WFS-T transactions. Lastly, eliminate the redudant visibility constraint when creating an index writer wip wip wip wip wip wip wip wip
rwgdrummer
pushed a commit
that referenced
this issue
Mar 22, 2016
# The first commit's message is: Issue #659, #658, #660. Allow the index writer to to multiple indices. Retain the index/adapter assocation to identify possibile indices to query for a given adapter and to enfore a consistent set of indices to write for a given adapter across multiple ingest runs or WFS-T transactions. Lastly, eliminate the redudant visibility constraint when creating an index writer wip wip wip wip wip wip wip wip wip # This is the 2nd commit message: wip # This is the 3rd commit message: wip # This is the 4th commit message: Issue #662. Partition based on boundary of polygon # This is the 5th commit message: GEOWAVE-669: moved geowavedemoapp to exmaples so that it could use adapter dependencies; demo app works in windows now # This is the 6th commit message: wip
rwgdrummer
pushed a commit
that referenced
this issue
Mar 22, 2016
# The first commit's message is: Issue #659, #658, #660. Allow the index writer to to multiple indices. Retain the index/adapter assocation to identify possibile indices to query for a given adapter and to enfore a consistent set of indices to write for a given adapter across multiple ingest runs or WFS-T transactions. Lastly, eliminate the redudant visibility constraint when creating an index writer wip wip wip wip wip wip wip wip wip wip wip Issue #662. Partition based on boundary of polygon GEOWAVE-669: moved geowavedemoapp to exmaples so that it could use adapter dependencies; demo app works in windows now wip wip # This is the 2nd commit message: Issue #659, #658, #660. Allow the index writer to to multiple indices. Retain the index/adapter assocation to identify possibile indices to query for a given adapter and to enfore a consistent set of indices to write for a given adapter across multiple ingest runs or WFS-T transactions. Lastly, eliminate the redudant visibility constraint when creating an index writer. GEOWAVE-669: moved geowavedemoapp to exmaples so that it could use adapter dependencies; demo app works in windows now
rwgdrummer
pushed a commit
that referenced
this issue
Mar 22, 2016
…. Retain the index/adapter assocation to identify possibile indices to query for a given adapter and to enfore a consistent set of indices to write for a given adapter across multiple ingest runs or WFS-T transactions. Lastly, eliminate the redudant visibility constraint when creating an index writer Issue #662. Partition based on boundary of polygon GEOWAVE-669: moved geowavedemoapp to exmaples so that it could use adapter dependencies; demo app works in windows now GEOWAVE-673: added index as optional parameter to KDE
rwgdrummer
added a commit
that referenced
this issue
Mar 22, 2016
…. Retain the index/adapter assocation to identify possibile indices to query for a given adapter and to enfore a consistent set of indices to write for a given adapter across multiple ingest runs or WFS-T transactions. Lastly, eliminate the redudant visibility constraint when creating an index writer Issue #659, #658, #660. Allow the index writer to to multiple indices. Retain the index/adapter assocation to identify possibile indices to query for a given adapter and to enfore a consistent set of indices to write for a given adapter across multiple ingest runs or WFS-T transactions. Lastly, eliminate the redudant visibility constraint when creating an index writer. GEOWAVE-669: moved geowavedemoapp to exmaples so that it could use adapter dependencies; demo app works in windows now Issue #659, #658, #660. Allow the index writer to to multiple indices. Retain the index/adapter assocation to identify possibile indices to query for a given adapter and to enfore a consistent set of indices to write for a given adapter across multiple ingest runs or WFS-T transactions. Lastly, eliminate the redudant visibility constraint when creating an index writer Issue #662. Partition based on boundary of polygon GEOWAVE-669: moved geowavedemoapp to exmaples so that it could use adapter dependencies; demo app works in windows now GEOWAVE-673: added index as optional parameter to KDE merged
This was referenced Mar 29, 2016
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Map<Index,Adapter[]>basically needs to be around to make decisions on which index to query if multiple indices exist. This required metadata should be stored and used in place of of RowRangeHistogram which is causing this issue currently: #655The text was updated successfully, but these errors were encountered: