NetarchiveSuite-Github

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
There actually exists methods in BitRepository to do this. You do NOT need to do anything special here... It is called replace, btw.

There actually exists methods in BitRepository to do this. You do NOT need to do anything special here...

It is called replace, btw.

There actually exists methods in BitRepository to do this. You do NOT need to do anything special here...

There actually exists methods in BitRepository to do this. You do NOT need to do anything special here...

There actually exists methods in BitRepository to do this. You do NOT need to do anything special here...

There actually exists methods in BitRepository to do this. You do NOT need to do anything special here...

There actually exists methods in BitRepository to do this. You do NOT need to do anything special here...

There actually exists methods in BitRepository to do this. You do NOT need to do anything special here...

Why? This should be entirely parallel to getFile...

Why? This should be entirely parallel to getFile...

How is the synchronization between existsInCollection and uploadFile? I.e. how long can you trust the file is not in the collection after having asked about it?

How is the synchronization between existsInCollection and uploadFile? I.e. how long can you trust the file is not in the collection after having asked about it?

Please do not require me to examine logs to get the result of my method calls. Or provide code for how I can programmatically read the recent log statements after having called this method, to figu...

Please do not require me to examine logs to get the result of my method calls. Or provide code for how I can programmatically read the recent log statements after having called this method, to figure out if the file was found or not...

this deserves a log.warn

this deserves a log.warn

bitrep does not have a close method?

bitrep does not have a close method?

Implement AutoClosable or remove the close methods. It is not very useful to be able to close a resource that is not closable

Implement AutoClosable or remove the close methods. It is not very useful to be able to close a resource that is not closable

Meaning that " " is an ok collectionId, right?

Meaning that " " is an ok collectionId, right?

perhaps worth a log statement...

perhaps worth a log statement...

Meaning that several store operations would each initialise the bitrepo

Meaning that several store operations would each initialise the bitrepo

This is not thread safe

This is not thread safe

please add this to the review

please add this to the review

odd indentation

odd indentation

NAS-2848 Default Collection for NAS/bitmag
NAS-2848 Default Collection for NAS/bitmag
Document about hdfs3 file security

    • -0
    • +19
    /mass-processing/HDFS File Security.md
Added a check that the CollectionID is known to the bitrepository.

Set CollectionID for upload to default to the NAS environment name.

Moved initialisation of bitrepository connection to first upload, so viewer instances don't need a valid bitmag config.

Fixed merge mess-up in pomfile.

Added a bunch of logging.

Added a bunch of logging.

    • -86
    • +31
    /quickstart/deploy_standalone_bitmag.xml
Added a bitmagasin client configuration for quickstart.

    • -0
    • +399
    /quickstart/deploy_standalone_bitmag.xml
Merge remote-tracking branch 'origin/bitmag' into bitmag

Added a bitmagasin client configuration for quickstart.

    • -0
    • +24
    /quickstart/bitmagclientconfig/logback.xml
Document about hdfs file security

    • -0
    • +31
    /mass-processing/HDFS File Security.md
Readme includes information about hadoop maven dependencies