Infobright Blog
Infobright Feature Requests
In my role at Infobright, I frequently work with many customers and prospects who express desires for capabilities that they feel they can't do with the current versions of Infobright. Sometimes that is the case - sometimes not. But where a need isn't aligned to a feature, function or methodology - whether it's a requirement, desire, or "nice to have" - I record and communicate that internally to Product Management and Engineering.
As many of you are aware, Infobright's origins are in the Data Warehousing, Business Intelligence and Analytics arena and therefore supported functionality was focused on those features and functions most commonly found and used in production environments. What might not be well-known is that our User Community has been educating us on other areas and use cases where Infobright is a particularly good fit for some of its core benefits around simplicity, ease of use, and low cost. And by moving into those new use cases, we have received requests for functionality that was not originally anticipated.
Consider this a formal request - What would you like to see in Infobright? Is it an absolute requirement, or a desired "nice to have" capability? Is it something that currently exists but you would like to see changed? Let me have it!
Here's an example:
"The Infobright Loader included with ICE is a high-performance load mechanism that absolutely blows away traditional techniques. It supports multiple file formats and has a certain degree of flexibility. But, as such, it is still a subset of MySQL's loader and offers a subset of its flexibility in format and execution. Continued refinement of the Infobright Loader toward complete alignment with the MySQL Loader would be welcomed."
Feel free to comment to this here on the blog posting, or post to our forums, or send me an email. I get them and appreciate them all!
Tags: OUR BLOGS
RECENT COMMENTS
[#8965] bobp22 comments on Become Our Next Community Manager
[#8964] darrensy comments on Using the MySQL JDBC Driver with Infobright for Data Loading
[#8963] gymnastic equipment comments on Become Our Next Community Manager
[#8962] gymnastic equipment comments on Become Our Next Community Manager
[#8961] Kate Rubik comments on Freewheel.tv Using Infobright Community Edition (ICE) in Production
[#8959] jerrycrook comments on Usage of Lookup Columns in Infobright
[#8958] ashleylare comments on Solutions to our Solutions
[#8957] Paul12 comments on Become Our Next Community Manager
[#8956] darrensy comments on Infobright and Analytics
[#8955] darrensy comments on Connecting Infobright and Talend
Chris,
Thanks for the suggestions! We really appreciate the feedback and guidance.
Without addressing each item in particular, I want you to know that all have been discussed and proposed to Product Management, Marketing and Engineering for consideration. I will add your comments to reinforce those previous discussions as well as “add some color” to them.
I hope to be able to address each in particular and in detail as soon as a decision has been agreed upon.
Thanks, again!
David Lutz
Hi David,
Thanks for giving us the opportunitiy to post our wishlist.
Here’s mine:
Absolute Requirement:
- Something like EXPLAIN for Infobright executor, or a way to test if a query is
executed by Infobright or by MYSQL before running a query ()
- Group by Function-Result (e.g date-functions)
Nice to have:
- and this one should be relatively easy: enable partitioning for MyISAM in the ICE release
- also enable by default some more engines, specifically BLACKHOLE, then the ICE could serve as a
true working machine only producing reports and posting into BLACKHOLE tables which are replicated to
slaves from where users can make heavily use of them w/o producing load on the ICE ..
- Some Form of Error Handling in LOAD, e.g. Some form of hickup in the data (particularly when migrating large datasets)
are to my experience not uncommon . If LOAD could simply skip and report those rows in a way that
rejected rows wont break the loading but are for instance written to a log table (whole row as text, no colums)
for further processing at a later time
(I am well aware that this is not SQL standard , but you asked for it: ).)
- SET Functionality in LOAD, which allows some minimal form of Transformation during LOAD in SQL
- CREATE [TEMPORARY] TABLE ... SELECT ... for Brighthouse , afaik it only works for MyISAM Engines.
I know this almost touches DML, which is reserved for IEE, but, again, you asked for it..
I am pretty sure I will come up with more soon ..
Post Comment