I believe you will only need one IPhysicalPropertiesVector instance.
The key role of this vector is to alert the system to use X number of
threads to process the work. Also the individual functions will then
used a specific thread to access the data they are responsible.
For example:
build-index-on-collection("path-to-collection-1|path-to-collection-2",
"path-to-index-1|path-to-index-2")
The example has two partitions. The IPhysicalPropertiesVector should
specify two partitions. Based on the partition id found in the
function runtime, you will pick which path to execute the designated
function. Both arguments, collection and index, will be available.
On Sat, Jul 16, 2016 at 10:52 PM, Menaka Madushanka
<[email protected]> wrote:
> Hello,
>
> When implementing VXQueryIndexingDatasource I came accross this issue.
>
> For delete and update queries, it takes only one argument, index directory.
>
> But for create index it takes two arguments collection directory and index
> directory.
> In parallelizing, both the arguments contains '|' delimited list of values.
>
> In VXQUeryCollectionDataSource, an IPhysicalPropertiesVector is created for
> the collection domain.
>
> I need to know the usage of IPhysicalPropertiesVector.
>
> And as create index has two similar arguments, do we need to create two
> IPhysicalPropertiesVector instances?
>
> Thank you very much
> Menaka
>
>
> --
> Menaka Madushanka Jayawardena
> Faculty of Engineering,
> University of Peradeniyaya.
> LinkedIn
> TP:- 071 885 1183/ 071 350 5470
