I think there is room for improvement in Amazon Athena, and the first thing I will put is the data output. I use Python to query in Amazon Athena, and it's very complex and difficult just to save Amazon Athena results as an Excel file. The only option is copying the data, but sometimes if it exceeds 100 lines, if you copy and paste in Excel, it's very bad. You can't copy above 100 lines. The other option is downloading a CSV file, but the CSV file is not UTF-8 Unicode. Here in Brazil, we speak Portuguese, and there are a lot of special characters in the words and even names, and everything gets garbled when you put it in a CSV. You have to decode, encode, and there are a lot of problems. It could easily save as an Excel file since there are a lot of engines to help with it, so an XLSX file extension could be this way. Another point I would mention is the word completion. When I'm coding and making statements and queries, Amazon Athena tries to help me write the code, and that's very problematic. Sometimes I'm using some tables that I use every day, and Amazon Athena doesn't get the tables I'm using and suggests very improbable data. I have access to more than 30 databases and hundreds of tables. So, I turn it off, I disable the word completion because when I'm coding, the word completion makes the coding slower. It's very difficult, and every time I have to press escape to skip the completion. It's very ineffective, so I disable it because in other applications it functions very well, such as VS Code.
Head of Data Practice at a tech consulting company with 201-500 employees
Real User
Top 10
2023-01-23T10:56:16Z
Jan 23, 2023
I think it would be better if the product were more mature. It's still a young product compared to Power BI or Qlik. I find that development is a bit difficult, but it might be because I'm used to other tools. The dashboarding capabilities could be better. The reporting and statement generation could be better. I couldn't technically initiate picture-perfect reporting, for example, to send out statements every month for banking customers.
Software Developer at a tech services company with 51-200 employees
Real User
2023-01-20T14:28:35Z
Jan 20, 2023
One improvement I can suggest is that Athena needs to work better with third-parties. For example, the process of querying a Microsoft SQL warehouse could be improved. When querying outside of AWS, you can use federated queries, but it's not always easy to do so.
Director & Lead Solutions Architect at Abylle Solutions
Real User
2022-12-19T12:29:59Z
Dec 19, 2022
The solution should include a better API for query services so that data can be dumped and queried directly in customer's products. The API should include some sort of data visualization that can be plugged into applications. We had to use QuickSight to help us with the visualization.
If you compare it with Palantir, if you have some data and you want to quickly have a look at it, then that feature is not available in Amazon Cloud. We'd like it better if, for example, when you have some data, you can easily query it and you can easily read it at a glance. We'd like it to just be almost like a drag-and-drop situation. In Amazon Cloud, you actually have first to upload the data into S3. For that, you have to create a bucket. Now you have to create a Glue service, which will get you the schema. Then that schema would create basically a database and a table. After that, you have to go to Athena to query the data. It's a three-step process in Amazon Cloud. In Palantir, you just have to drag and drop.
Search as a Service enhances how users interact with data by providing robust search capabilities, making information retrieval more efficient and accurate.
Search as a Service leverages advanced algorithms and machine learning to provide fast, relevant search results. It integrates seamlessly with diverse platforms, supporting scalable, real-time data retrieval. Organizations benefit by reducing time spent on locating information and increasing productivity.
What are the...
I think there is room for improvement in Amazon Athena, and the first thing I will put is the data output. I use Python to query in Amazon Athena, and it's very complex and difficult just to save Amazon Athena results as an Excel file. The only option is copying the data, but sometimes if it exceeds 100 lines, if you copy and paste in Excel, it's very bad. You can't copy above 100 lines. The other option is downloading a CSV file, but the CSV file is not UTF-8 Unicode. Here in Brazil, we speak Portuguese, and there are a lot of special characters in the words and even names, and everything gets garbled when you put it in a CSV. You have to decode, encode, and there are a lot of problems. It could easily save as an Excel file since there are a lot of engines to help with it, so an XLSX file extension could be this way. Another point I would mention is the word completion. When I'm coding and making statements and queries, Amazon Athena tries to help me write the code, and that's very problematic. Sometimes I'm using some tables that I use every day, and Amazon Athena doesn't get the tables I'm using and suggests very improbable data. I have access to more than 30 databases and hundreds of tables. So, I turn it off, I disable the word completion because when I'm coding, the word completion makes the coding slower. It's very difficult, and every time I have to press escape to skip the completion. It's very ineffective, so I disable it because in other applications it functions very well, such as VS Code.
You have to build out the metadata yourself because of the nature of the cloud.
I think it would be better if the product were more mature. It's still a young product compared to Power BI or Qlik. I find that development is a bit difficult, but it might be because I'm used to other tools. The dashboarding capabilities could be better. The reporting and statement generation could be better. I couldn't technically initiate picture-perfect reporting, for example, to send out statements every month for banking customers.
One improvement I can suggest is that Athena needs to work better with third-parties. For example, the process of querying a Microsoft SQL warehouse could be improved. When querying outside of AWS, you can use federated queries, but it's not always easy to do so.
The solution should include a better API for query services so that data can be dumped and queried directly in customer's products. The API should include some sort of data visualization that can be plugged into applications. We had to use QuickSight to help us with the visualization.
If you compare it with Palantir, if you have some data and you want to quickly have a look at it, then that feature is not available in Amazon Cloud. We'd like it better if, for example, when you have some data, you can easily query it and you can easily read it at a glance. We'd like it to just be almost like a drag-and-drop situation. In Amazon Cloud, you actually have first to upload the data into S3. For that, you have to create a bucket. Now you have to create a Glue service, which will get you the schema. Then that schema would create basically a database and a table. After that, you have to go to Athena to query the data. It's a three-step process in Amazon Cloud. In Palantir, you just have to drag and drop.