In latest DBSight release, there are 2 features that we liked so much that we urge your to try them out!
1) Virtual index. It can aggregate several index search results in one page. And those indexes can be on a separated DBSight installation! So you can literally aggregate lots of search in one single page!
2) Data Grid scaffold. It's a feature-loaded powerful scaffold. It can turn data in your common table or views into a full-text searchable data grid, with facet search, sorting, csv export, fullscreen support, infinite scroll, detail page, etc. It's something you can start from a SQL and turn to a professional-looking search page, presentable to your CEO!
I would like to tell you that IBM bought licenses from us!
It's not a big amount, but makes us happy since IBM surely has its own search software.
Integrating DBSight with your application now becomes super easy!
Of course, you can customize the text, stylesheet, etc. The API is improving and please tell us what you want!
The details can be found in the shipped javadoc. We will update the wiki, scaffolding, soon.
It is hard to see JVM struggles with garbage collection. The CPU fan spins fast and the disk makes a loud noise. OK. JVM, I see you are working hard. But the request hangs and users are waiting.
Why not just kill it and create a new one?
This is what DBSight 4.x did.
DBSight 4.x defaults to a separated searching mode. Each time, a dedicated search process is launched to specifically serve all the search request. If the index is updated, a new search process is created and the previous search process is stopped. Here are some benefits:
+ Stopping a search process is actually much faster for large indexes, than waiting for JVM.
Now you can create an index via customized fetcher, and select the SalesForce.com adapter, fill in username/password and the object you want to search on, like "Account".
The rest is exactly the same as ordinary database search configuration.
The good thing is, the incremental indexing will also work. You just schedule the job. And on SalesForce.com side, you need to make the object replicable. This replicable setting doesn't matter if you create index from scratch.
As your data grows, one single box can not hold all of your data. So what to do? Buy a bigger box or add another box?
Getting a bigger box may work for some. Actually it's much simpler and cost less on man-hours. A few thousands of dollars are much cheaper than putting several developers on it.
Of course, Sharded Search can go further by just adding more computer boxes.
DBSight can now support sharded search now! And you don't need to do much. Just adjust the search URL!
Suppose you are 2 indexes on 2 different boxes. The URL format is pretty simple, just say:
This is an interesting feature!
Usually if you have several DBSight servers, you may have to log on to several servers to copy index configurations. And sometimes it is hard to track which one has the latest change.
For Enterprise licenses, to use the Remote Index Replication feature, you also need to setup where the master index is.
Now everything is just one click away!
If you have the remote DBSight server's password, you can browse the local network, copy the remote index configuration and templates with one click!
One user, Rajendra, asked for a new feature: copy the index configuration.
It is a basic operation that we have missed all along!
DBSight can create, delete, and even upload index configurations. But "copy".... duh! Thanks Rajendra!
We have spent a little time to add it in. Hopefully you will like it. Now you could easily manage all the index configurations, make it easier for you to develop, test, and put DBSight to production.
Please let us know any feature you want. We will add it if it's a good feature.
Brand New feature not seen anywhere else!
Normally when you do a facet search, you get how many hits for that facet. This is a great feature. But there is more!
Now wiht 2.1.6 beta, you can also get Sum and Average for a different field!
It's just like SQL:
select count(*), sum(f2),avg(f2) from t group by f1
If you are upgrading to 2.1.3, you may need to re-create the whole index. This is because the storage format of time is changed, to allow support for time before 1970.
This is a rather big change, so please pay attention to it.