• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • Devaka Cooray
  • Ron McLeod
  • Jeanne Boyarsky
Sheriffs:
  • Liutauras Vilda
  • paul wheaton
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Piet Souris
  • Carey Brown
  • Tim Holloway
Bartenders:
  • Martijn Verburg
  • Frits Walraven
  • Himai Minh

what persistence technology should I use for indexing

 
Ranch Hand
Posts: 129
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I'm developing a JSF application, where I have all the objects sorted out (using good old inheritance and association) .

Obviously, I plan to save this data somewhere. First thing came to mind is stored as objects into a relational database. But I fear that might cause a problem since I plan to use indexing later (such Apache Solr), so I fear just storing data as objects might might hinder indexing.

Would it be a good idea to store the data as a flat file? Or is there another technology I need to look for? I guess my question is, what options to I have ?


 
Ranch Hand
Posts: 270
15
Android Angular Framework Spring AngularJS Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
JSF would make a good match for JPA. As for options, you can do something like divide your data into flat text 'bulk' vs things that make sense for relational. Then you could use the relational to store "handles" (locators of some kind) for fetching back the flat files. Later, when you want SOLR queries, you can just index them where the files are. That's one option.

Another: Oracle used to have its own implementation for textual indexing. MySQL--I do not know.

And finally: if you think you will ditch all relational at some point, place all access behind a DAO, to be reimplemented as you see fit.
 
Ali Khalfan
Ranch Hand
Posts: 129
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I will try to start by just using JPA and store everything in a relational database than maybe use elasticsearch. I will see how that works

 
This tiny ad will self destruct in five seconds.
the value of filler advertising in 2021
https://coderanch.com/t/730886/filler-advertising
reply
    Bookmark Topic Watch Topic
  • New Topic