Fixed it

I was able to get my project working again, while still using Lucene. I attempted to switch to MySQL, but after trying to install it on my Raspberry Pi, the Pi no longer turns on. I mentioned to a co-worker that I was having this issue, and they pointed out that a sql server needs a fair amount of resources, so I'm not sure if my Raspberry Pi will be able to handle it. I don't expect the database to be very large, but that might still be a problem. Anyway, I need to get that started up, so thats bonna be my next step.

Once I noticed that the pi wasn't able to start up, I was too lazy to move the pi, to somewhere I can use a monitor, mouse, and keyboard, so I went back to work on trying to fix my problem with lucene. I started by looking for Luke again, which would allow me to view the lucene index. When I first started working on this, but at the time I wasn't able to find it for the version of Luke I was using. I was able to find it this time however.

By using Luke I was able to determine that my problem was that the id on my objects was not the same as the id that is indexed. I generated the id by using a hash of the path to the file, but during the refactor, I changed the implementation of what I store for the path, which caused the hash to change. This was causing the id that was searched for to not exist, and return no results. I fixed this by using the id from the lucene document if thats how it was created.

So now my site is working properly, I will not be touching it again, until I get it in source control, but to do that I have to get my Raspberry Pi to a point where it can start up, so it can be my GIT server.