PILLUTLAAVINASH / google-enterprise-connector-manager

Automatically exported from code.google.com/p/google-enterprise-connector-manager
0 stars 0 forks source link

Provide some type of Awareness Interface to the Connectors that allows them to get status on documents sent to the sink #151

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Currently Connectors are not notified if a document has problems being 
processed on the sink - in this case the GSA.  For example, if a document 
can't be converted or if a delete request was not successful then the 
Connector will not have an accurate picture of document on the sink.

Also the Connectors that maintain a view of documents sent may not have an 
accurate image as the sink has problems.

One implementation may be to send a request to the Connector to resend a 
batch of specified documents or patterns of documents.  May involve a batch 
larger than the batch hint.

Another implementation may be to send the Connector a snapshot of the sink 
image every so often.

Original issue reported on code.google.com by mgron...@gmail.com on 6 May 2009 at 10:27

GoogleCodeExporter commented 8 years ago
See Otex Issue 26.

Maybe a command line tool for the case where need to feed a new chunk of 
documents to 
the GSA.

Might want to break this up into two Issues since one focused on asking the 
Connector 
to resend a specified set of documents and the other is related to getting an 
state 
image of those documents on the sink (GSA).

Original comment by mgron...@gmail.com on 6 May 2009 at 10:33

GoogleCodeExporter commented 8 years ago

Original comment by mgron...@gmail.com on 6 May 2009 at 11:16

GoogleCodeExporter commented 8 years ago

Original comment by jl1615@gmail.com on 18 Sep 2009 at 8:35

GoogleCodeExporter commented 8 years ago
This will be supported when the GData support is integrated into the CM.

Original comment by mar...@google.com on 1 Dec 2009 at 12:24

GoogleCodeExporter commented 8 years ago

Original comment by mar...@google.com on 4 Dec 2009 at 11:29

GoogleCodeExporter commented 8 years ago

Original comment by mar...@google.com on 5 Dec 2009 at 12:00

GoogleCodeExporter commented 8 years ago
See also issue 200 and 202

Original comment by Brett.Mi...@gmail.com on 12 Mar 2010 at 11:20

GoogleCodeExporter commented 8 years ago
This issue is filed as Google issue #6513593

Original comment by tdnguyen@google.com on 18 May 2012 at 9:23