Speed up huge information analytics with the Glow 3.0 suitable port for SQL Server– now in sneak peek.
We are revealing that the sneak peek release of the Apache Glow 3.0 suitable Apache Glow Port for SQL Server and Azure SQL, offered through Maven.
Open sourced in June 2020, the Apache Glow Port for SQL Server is a high-performance port that allows you to utilize transactional information in huge information analytics and continue outcomes for ad-hoc questions or reporting. It enables you to utilize SQL Server or Azure SQL as input information sources or output information sinks for Glow tasks. To date, the port supported Glow 2.4 work, and now, you can utilize the port as you make the most of the numerous advantages of Glow 3.0 too.
Why utilize the Apache Glow Port for SQL Server and Azure SQL
The Apache Glow Port for SQL Server and Azure SQL is based upon the Apache Glow DataSourceV1 API and SQL Server Bulk API and utilizes the exact same user interface as the integrated Java Database Connection (JDBC) Spark-SQL port. This enables you to quickly incorporate the port and move your existing Glow tasks by merely upgrading the format specification.
Significant functions and advantages of the port:
. • Suitable with Apache Glow 3.0.
. • Assistance for all Apache Glow bindings (Scala, Python, R).
• Standard authentication, Active Directory site (ADVERTISEMENT) Secret Tab, and Azure Active Directory site assistance.
To get more information about the port and how to utilize it, check out the GitHub page. The 3.0 suitable port is offered through the spark-mssql-connnector_2.12 _ 3.0:1.0.0- alpha Maven coordinate.
The Apache Glow Port for SQL Server and Azure SQL makes the interaction in between SQL Server and Apache Glow perfect. The port has a growing and engaged neighborhood and has actually been set up countless times. We are continually progressing and enhancing the port, and we anticipate your feedback and contributions.
Wish to contribute or have feedback or concerns? Take a look at the task on GitHub and follow us on Twitter.
Note: The port is neighborhood supported and does not consist of Microsoft SLA assistance. Please submit a concern on GitHub to engage the neighborhood for assistance.