Presto is an open source SQL query engine designed to run queries on data stored in Hadoop or in traditional databases.
Teradata supported development of Presto followed the acquisition of Hadapt and Revelytix.
N/A
REDCap
Score9 out of 10
N/A
REDCap is a secure web application designed by Vanderbilt University to build and manage online surveys and databases in a research setting for universities.
While REDCap can be used to collect virtually any type of data in any environment (including compliance with 21 CFR Part 11, FISMA, HIPAA, and GDPR), it is specifically geared to support online and offline data capture for research studies and operations.
Presto is for interactive simple queries, where Hive is for reliable processing. If you have a fact-dim join, presto is great..however for fact-fact joins presto is not the solution.. Presto is a great replacement for proprietary technology like Vertica
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
Linking, embedding links and adding images is easy enough.
Once you have become familiar with the interface, Presto becomes very quick & easy to use (but, you have to practice & repeat to know what you are doing - it is not as intuitive as one would hope).
Organizing & design is fairly simple with click & drag parameters.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
Customization. I can use HTML to change format but there are also a ton of built in functionality for branching logic, matrix configuration, slider scales, etc.
Security. HIPPA compliance is extremely important for medical research and REDCap ensures our data is safe.
Variety of use. Being able to send both surveys and create forms for internal use makes the use cases numerous.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
Presto was not designed for large fact fact joins. This is by design as presto does not leverage disk and used memory for processing which in turn makes it fast.. However, this is a tradeoff..in an ideal world, people would like to use one system for all their use cases, and presto should get exhaustive by solving this problem.
Resource allocation is not similar to YARN and presto has a priority queue based query resource allocation..so a query that takes long takes longer...this might be alleviated by giving some more control back to the user to define priority/override.
UDF Support is not available in presto. You will have to write your own functions..while this is good for performance, it comes at a huge overhead of building exclusively for presto and not being interoperable with other systems like Hive, SparkSQL etc.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
It is very interesting to me especially that it meets all my needs. The libraries makes the job even much easier, since you can just make a few adjustments to the appropriate template chosen
Presto is good for a templated design appeal. You cannot be too creative via this interface - but, the layout and options make the finalized visual product appealing to customers. The other design products I use are for different purposes and not really comparable to Presto.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
SurveyMonkey and Google Forms have similar features for surveys but they lack the form options and user interface. They are also not HIPPA compliant so we are not able to collect any identifying information which is usually an issue in research when we are tracking participants. Many institutional review boards won't even approve a study without a HIPPA compliant data collection service.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
REDCap allowed us to house all patient information in one single portal which helped us eliminate the need for paper copies. We moved our whole filing system to an electronic version when we became "live" on REDCap. It is also very convenient and accessible to have all of this data in one location.
A very positive impact is the ability for multiple users to see the same health and wellness information for each specific patient. Instead of constantly having to go back and forth via email, phone, etc. to ask about the patient; we could simply look up their information in REDCap and find all of the answers. It made our business much more efficient and made the patients feel as though we did our research prior to meeting with them.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
