Hi Sithumini, Few more queries regarding the Advanced search implementation.
> *Findings* > Below table1 demonstrate the data fields and types currently being indexed > and which have to index with the new feature. > > *Currently Indexing data fields* > > *Field Type* > > *Data fields to be index with new feature* > > *Field Type* > > id > > String field > > Resource Name > > String field > > tenantId > > String field > > Created from date > > Date field > > contentOnly > > String field > > Created to date > > Date field > > timestamp > > String field > > Updated from date > > Date field > > text > > String field > > Updated to date > > Date field > > > > Created by > > String field > > > > Updated by > > String field > > > > Tags > > MultiValued field > > > > Comments > > MultiValued field > > > > Association Type > > MultiValued field > > > > Association Destination > > MultiValued field > > > > Property Name > > MultiValued field > > > > Property Value > > MultiValued field > > > > Media Type > > String field > Table1 > Addition to the above index fields, we have some dynamic fields and also fields which are currently indexed is depends on the indexer defined for the particular resource type. for example, in RXTIndexer, we are indexing, media type LC state LC Name Artifact attributes etc. But for Advanced search, we need to enforce fields required to advanced search in every index document. So only having default indexer will not address the problem. We need to enforce index those fields in current existing indexers and indexer defined in future. How are we going to cater this problem. Thanks -- Danesh Kuruppu Software Engineer WSO2 Inc, Mobile: +94 (77) 1690552
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
