I had the same problem with a database here, and we discovered that every item had its own product page, its own url. So, we decided that our unique id had to be the url instead of using sql ids and id concatenations. sometimes it works. You can store all ids if u need them for something, but for uniqueids, urls go just fine.
2011/8/30 Erick Erickson <erickerick...@gmail.com> > I'd really think carefully before disabling unique IDs. If you do, > you'll have to manage the records yourself, so your next > delta-import will add more records to your search result, even > those that have been updated. > > You might do something like make the uniqueKey the > concatenation of productid and attributeid or whatever > makes sense. > > Best > Erick > > On Mon, Aug 29, 2011 at 5:52 PM, Aaron Bains <aaronba...@gmail.com> wrote: > > Hello, > > > > I am trying to setup Solr Faceting on products by using the > > DataImportHandler to import data from my database. I have setup my > > data-config.xml with the proper queries and schema.xml with the fields. > > After the import/index is complete I can only search one productid record > in > > Solr. For example of the three productid '10100039' records there are I > am > > only able to search for one of those. Should I somehow disable unique > ids? > > What is the best way of doing this? > > > > Below is the schema I am trying to index: > > > > +-----------+-------------+---------+------------+ > > | productid | attributeid | valueid | categoryid | > > +-----------+-------------+---------+------------+ > > | 10100039 | 331100 | 1580 | 10000 | > > | 10100039 | 331694 | 1581 | 10000 | > > | 10100039 | 33113319 | 1537370 | 10000 | > > | 10100040 | 331100 | 1580 | 10000 | > > | 10100040 | 331694 | 1540230 | 10000 | > > | 10100040 | 33113319 | 1537370 | 10000 | > > +-----------+-------------+---------+------------+ > > > > Thanks! > > > -- *Alexei Martchenko* | *CEO* | Superdownloads ale...@superdownloads.com.br | ale...@martchenko.com.br | (11) 5083.1018/5080.3535/5080.3533
