Unless you have a real problem with space limitations, I would think that paying the time up front for loading in exchange for much better query behavior over the life of the database would be a good bargain.
Adam > On Apr 13, 2018, at 9:28 AM, Andy Seaborne <[email protected]> wrote: > > > > On 13/04/18 12:17, Samita Bai / PhD CS Scholar @ City Campus wrote: >> Thanks dear Andy. But can you tell me how to declare StoreParams? >> Well I am trying to index Dynamic Linked Data Observatory's data, which is >> quite huge so it is taking me a lot of time so I thought if I create one >> index instead of many then it can help me saving time as well as space. >> Please let me know if I am thinking correct or not? > > You may be better off with TDB1 which has a better bulk loader. > > Andy > >> Regards, >> Samita Bai >> ________________________________ >> From: Andy Seaborne <[email protected]> >> Sent: 13 April 2018 15:43:27 >> To: [email protected] >> Subject: Re: TDB2 store parameters >> Hi Samita, >> That capability is in the public API yet but it exists >> You can set the StoreParams if you go in at a low level. >> The easiest way is probably call >> DatabaseConnection.connectCreate(Location, StoreParams) >> then either use the returned DatabaseConnection.getDatasetGraph or >> ignore the restuned object and call >> TDB2Factory.connectDatabase(Location) >> because the first call sets up the database and keeps an internal >> permanent handle, then the second call uses that to build a dataset. >> This documentation for TDB1 >> https://jena.apache.org/documentation/tdb/store-parameters.html >> applies >> and the tests in TestStoreParams may help you (NB versions in TDB1 and >> TDB2 so check the right class) >> This is a fragile mechanism, which si why it isn't that visible. >> StoreParams for index choices can only be set when the DB is first >> created and the same StoreParams for the file naming must be used each >> time or else the database will be corrupted. >> This area is not heavily tested. Queries can end up very slow if there >> is no appropriate index. >> For background, why do you want to modify the index choice to just GSPO? >> Andy >> On 13/04/18 07:47, Samita Bai / PhD CS Scholar @ City Campus wrote: >>> Hello, >>> >>> >>> I want to store only one index in TDB2 i.e. GSPO, instead of all >>> combinations. How can I do it? I read some documentation and got to know >>> that it can be done with the help of store parameters but I am not finding >>> any help how to call that config file from code. >>> >>> >>> Please guide me. >>> >>> >>> Regards, >>> >>> Samita Bai >>> >>> P : Please consider the environment before printing this e-mail >>> >>> ________________________________ >>> >>> CONFIDENTIALITY / DISCLAIMER NOTICE: This e-mail and any attachments may >>> contain confidential and privileged information. If you are not the >>> intended recipient, please notify the sender immediately by return e-mail, >>> delete this e-mail and destroy any copies. Any dissemination or use of this >>> information by a person other than the intended recipient is unauthorized >>> and may be illegal. >>> >>> ________________________________ >>> >> P : Please consider the environment before printing this e-mail >> ________________________________ >> CONFIDENTIALITY / DISCLAIMER NOTICE: This e-mail and any attachments may >> contain confidential and privileged information. If you are not the intended >> recipient, please notify the sender immediately by return e-mail, delete >> this e-mail and destroy any copies. Any dissemination or use of this >> information by a person other than the intended recipient is unauthorized >> and may be illegal. >> ________________________________
