You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: HDInsight supports multiple deployable Hadoop cluster components and versions. See the Hadoop and HortonWorks Data Platform (HDP) distribution versions supported.
3
+
description: Learn the Hadoop components and versions in HDInsight and the service levels available in this cloud distribution of HortonWorks Data Platform.
4
4
services: hdinsight
5
5
editor: cgronlun
6
6
manager: jhubbard
@@ -20,7 +20,7 @@ ms.author: saurinsh
20
20
---
21
21
# What are the different Hadoop components and versions available with HDInsight?
22
22
23
-
Find out about the different service levels offered by HDInsight, as well as the versions of different Hadoop components included.
23
+
Learn about the service levels offered for Azure HDInsight, as well as the Hadoop ecosystem components and versions included. Each HDInsight version is a cloud distribution of a version of the HortonWorks Data Platform (HDP).
24
24
25
25
## HDInsight Standard and HDInsight Premium
26
26
@@ -110,7 +110,7 @@ The SLA is defined in terms of a "Support Window". A Support Window refers to th
110
110
* Formula 1: Add 180 days to the date HDInsight cluster version X was released.
111
111
* Formula 2: Add 90 days to the date HDInsight cluster version X+1 (the subsequent version after X) is made available in the Portal.
112
112
113
-
The **Deprecation Date** is the date after which the cluster version cannot be created on HDInsight. Starting July 31st 2017, you cannot resize a cluster after it's deprecation date.
113
+
The **Deprecation Date** is the date after which the cluster version cannot be created on HDInsight. Starting July 31st 2017, you cannot resize a cluster after it's deprecation date.
114
114
115
115
> [!NOTE]
116
116
> Windows-based HDInsight cluster (including version 2.1, 3.0, 3.1, 3.2 and 3.3) run on Azure Guest OS Family 4, which uses the 64-bit version of Windows Server 2012 R2 and supports .NET Framework 4.0, 4.5, 4.5.1, and 4.5.2.
Copy file name to clipboardExpand all lines: articles/logic-apps/logic-apps-enterprise-integration-metadata.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,18 +25,18 @@ Partners, agreements, schemas, maps added to an integration account, store metad
25
25
26
26
## How to Store metadata
27
27
28
-
1. Create an [Integration Account](../logic-apps/logic-apps-enterprise-integration-create-integration-account.md)
28
+
1. Create an [Integration Account](logic-apps-enterprise-integration-create-integration-account.md)
29
29
30
-
2. Add a [partner](logic-apps-enterprise-integration-partners.md#how-to-create-a-partner) or an [agreement](../logic-apps/logic-apps-enterprise-integration-agreements.md#how-to-create-agreements) or a [schema](logic-apps-enterprise-integration-schemas.md) in integration account
30
+
2. Add a [partner](logic-apps-enterprise-integration-partners.md#how-to-create-a-partner) or an [agreement](logic-apps-enterprise-integration-agreements.md#how-to-create-agreements) or a [schema](logic-apps-enterprise-integration-schemas.md) in integration account
31
31
32
32
3. Select a parter or an agreement, or a schema. select **Edit as JSON** and enter metadata details
## Call **Integration Account Artifact LookUp** from a logic app
36
36
37
-
1. Create a [Logic App](../logic-apps/logic-apps-create-a-logic-app.md)
37
+
1. Create a [Logic App](logic-apps-create-a-logic-app.md)
38
38
39
-
2.[Link](../logic-apps/logic-apps-enterprise-integration-create-integration-account.md#how-to-link-an-integration-account-to-a-logic-app) Logic App with an Integration Account
39
+
2.[Link](logic-apps-enterprise-integration-create-integration-account.md#how-to-link-an-integration-account-to-a-logic-app) Logic App with an Integration Account
40
40
41
41
3. Create a trigger, for example using *Request* or *HTTP* before searching for **Integration Account Artifact LookUp**. Search **integration** to look for **Integration Account Artifact LookUp**
Copy file name to clipboardExpand all lines: articles/logic-apps/logic-apps-securing-a-logic-app.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -85,7 +85,7 @@ A valid IP range takes the format `192.168.1.1/255`. If you want the logic app
85
85
86
86
#### Setting IP ranges on the resource definition
87
87
88
-
If you are using a [deployment template](../logic-apps/logic-apps-create-deploy-template.md) to automate your deployments, the IP range settings can be configured on the resource template.
88
+
If you are using a [deployment template](logic-apps-create-deploy-template.md) to automate your deployments, the IP range settings can be configured on the resource template.
89
89
90
90
```json
91
91
{
@@ -138,7 +138,7 @@ This setting can be configured within the resource settings of the Azure portal:
138
138
139
139
#### Setting IP ranges on the resource definition
140
140
141
-
If you are using a [deployment template](../logic-apps/logic-apps-create-deploy-template.md) to automate your deployments, the IP range settings can be configured on the resource template.
141
+
If you are using a [deployment template](logic-apps-create-deploy-template.md) to automate your deployments, the IP range settings can be configured on the resource template.
142
142
143
143
```json
144
144
{
@@ -252,15 +252,15 @@ When working with an HTTP, HTTP + Swagger (Open API), or Webhook action, you can
252
252
253
253
### Restricting access to logic app IP addresses
254
254
255
-
All calls from logic apps come from a specific set of IP addresses per region. You can add additional filtering to only accept requests from those designated IP addresses. A list of those IP addresses can be found [in this article](../logic-apps/logic-apps-limits-and-config.md#configuration).
255
+
All calls from logic apps come from a specific set of IP addresses per region. You can add additional filtering to only accept requests from those designated IP addresses. A list of those IP addresses can be found [in this article](logic-apps-limits-and-config.md#configuration).
256
256
257
257
### On-premises connectivity
258
258
259
259
Logic apps provides integration with a number of services to provide secure and reliable on-premises communication.
260
260
261
261
#### On-premises data gateway
262
262
263
-
Many of the managed connectors from logic apps provide secure connectivity to on-premises systems, including File System, SQL, SharePoint, DB2, and more. The gateway leverages encrypted channels via Azure Service Bus to relay data on-premises, and all traffic originates from secure outbound traffic from the gateway agent. More details on how the gateway works [in this article](../logic-apps/logic-apps-gateway-install.md#how-the-gateway-works).
263
+
Many of the managed connectors from logic apps provide secure connectivity to on-premises systems, including File System, SQL, SharePoint, DB2, and more. The gateway leverages encrypted channels via Azure Service Bus to relay data on-premises, and all traffic originates from secure outbound traffic from the gateway agent. More details on how the gateway works [in this article](logic-apps-gateway-install.md#how-the-gateway-works).
264
264
265
265
#### Azure API Management
266
266
@@ -271,7 +271,7 @@ Many of the managed connectors from logic apps provide secure connectivity to on
271
271
You can use the on-premises hybrid connection feature for Azure API and Web apps to communicate on-premises. Details on hybrid connections and how to configure can be found [in this article](../app-service-web/web-sites-hybrid-connection-get-started.md).
272
272
273
273
## Next steps
274
-
[Create a deployment template](../logic-apps/logic-apps-create-deploy-template.md)
274
+
[Create a deployment template](logic-apps-create-deploy-template.md)
0 commit comments