On Thu, Jun 16, 2011 at 10:30 PM, George Niculae <[email protected]> wrote:
> On Thu, Jun 16, 2011 at 10:22 PM, Mircea Carasel <[email protected]> > wrote: > > > > > > On Thu, Jun 16, 2011 at 3:16 PM, George Niculae <[email protected]> > wrote: > >> > >> Hi All, > >> > >> re XX-9686: LDAP: import stops if connection is closed > >> right now while importing users from LDAP we're connecting for each > >> entry and retrieve attributes for. However if the connection to LDAP > >> is dropped during this operation a runtime exception is throw and the > >> import background task dies. > >> Since data needed to import is already available in a csv file > >> (generated at preview) I am thinking that we could replace the > >> existing LDAP import with a plain csv import. Or at least for 4.4 to > >> put a download link for getting the csv file, then admin to manually > >> import it if needed... > >> > > If ldap entries are already saved in a .csv file during preview, I see > no > > reason to connect once again during import, to force ldap connection. > Import > > will be faster if we read from .csv. But IMO we still need to offer the > > option to "refresh" the .csv file. > > LDAP content may get changed independent of sipxecs, so when the > > administrator decides, we need to offer him the posibility to synchronise > > the csv content with LDAP > > > > Check "Enable periodic import from LDAP" option in Import tab and you > have periodic synch of data > That's perfect > The point is: when we're doing such LDAP imports should we query LDAP > for each and every entry or should we dump first data in csv file and > make a plain csv import after? > > Making a query to get attribute values for each user looks really bad to me. If you have 1000 users means 1000 queries in LDAP to get attribute values. I am not surprised that connection goes down at some point :) Dumping data in csv and making csv import after, looks like a brilliant idea to me. Just make sure csv contains all you need. In addition, there will be one single piece of code to maintain, instead of two Mircea > George > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ >
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
