Indexing of SQL Connector taking excessively long to complete

[Ben Hines]

Hello,

I have a connector that produces about 50K signals and conditions.  Yesterday, I updated the configuration to add a property that gets populated by an SQL statement.  It should not produce any additional signals or conditions as compared to the previous indexing operation.  Apparently this is a very time-consuming addition as the indexing of the configuration as been running over night and is still chugging away.

Clearly, I need to make this more efficient.  My question, though, is what happens to existing signals and conditions if I cancel the current indexing operation?  Specifically, if the previous index produced 50K signals+conditions and the current indexing operation is canceled after, say, 30K signals+conditions have been indexed, what happens to the remaining 20K signals+conditions?