20 Jun, 2007

1 commit

  • - Extracted common interface DatabaseContainer from DN2ID, ID2Entry, etc... classes.
    - Moved database read and write methods from EntryContainer to DatabaseContainer.
    - Added index configuration to the XML based admin framework.
    - Removed redundant configuration objects (Config, IndexConfig).
    - Added exclusive/shared lock to EntryContainer. All access to an EntryContainer must acquire a lock before using the internal 
    DatabaseContainers or making configuration changes.
    - Added the ability to add/remove/modify indexes with the backend online. Server will issue rebuild required warning when adding new indexes 
    or sub-indexes (equality, substring, presence...).
    - Added the ability to change the index entry limit for both the backend and each index with the backend online. Server will issue rebuild 
    required warning if the previous limit has been exceeded.
    - Added the ability to change entry compression and index substring length setting while the backend is online.
    - Added a persistent state database to each EntryContainer to persist backend configuration between server restarts. Server will issue 
    rebuild required warning if a new index is added when the backend is offline.
    - Added a trusted flag to indexes so that non existent keys will not be interpreted as an empty entry ID set when an index is untrusted. An 
    index is untrusted when it is added to an non-empty EntryContainer or an inconsistency is detected. Server will issue warning on startup to 
    rebuild the index. 
    - Fixed a issue where the LDIF import process stops responding if the temporary import dir is full or unwritable. 
    
    Fix for issue 1480 1455 1575
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2135 41b1ffd8-f28e-4786-ab96-9950f0a78031
    boli
     

19 Jun, 2007

1 commit


18 Jun, 2007

2 commits


17 Jun, 2007

1 commit


15 Jun, 2007

7 commits


14 Jun, 2007

8 commits


13 Jun, 2007

3 commits


12 Jun, 2007

7 commits


11 Jun, 2007

5 commits


08 Jun, 2007

1 commit


07 Jun, 2007

4 commits

  • use a privilege of "unindexed-search" instead.  Also, eliminate the
    index-rebuild privilege and fold all of its functionality into ldif-import,
    since having a separate privilege for it doesn't provide much benefit and
    creates additional administrative overhead.
    
    OpenDS Issue Numbers:  1765, 1776
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2051 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • for entries in private backends (e.g., the root DSE, schema, monitor entries,
    config entries, etc.).  The entryUUID value that will be generated is based on
    an MD5 hash of the entry DN, but this shouldn't be a problem for entries in
    private backends because none of them allow modify DN operations.  User entries
    should have a real entryUUID value generated when the entry is created (either
    via an LDAP add or an LDIF import).
    
    OpenDS Isssue Number:  1775
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2050 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • element that includes flags that indicate how the entry was encoded.  The
    flags currently defined include:
    
    - Whether to exclude the DN from the encoded entry.  This may be useful for the
      filesystem entry cache, since it will already have a reference to the DN.
    
    - Whether to compress the set of object classes contained in the entry with a
      binary token.
    
    - Whether to compress the attribute descriptions in the entry with binary
      tokens.
    
    These changes can help improve the encode/decode performance, and can reduce
    the entry footprint (by about 30% for entries based on the example.template).
    None of these options are enabled at the present time, but components which
    call the Entry.encode() method will be able to indicate which of them should be
    used for that entry.
    
    OpenDS Issue Numbers:  660, 1675, 1770
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2049 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • Considering the limited added value that the JMX port will provide on 1.0 and the fact that we do not want to expose it on the QuickSetup, in the admin group we consider to disable this port by default.  Before committing a fix for this maybe we should send a Heads Up message to the users mailing list.
    
    Basically after the changes the JMX connection handler will not be enabled if the server is installed using the graphical setup.  For the command line setup, JMX will not be enabled unless the user explicitly includes de -x option (for the JMX port) when invoking the command-line.
    
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2046 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara