ClickHouse/docs/en/sql-reference/functions/url-functions.md

423 lines
13 KiB
Markdown
Raw Normal View History

2020-04-03 13:23:32 +00:00
---
toc_priority: 54
2020-06-19 10:15:32 +00:00
toc_title: URLs
2020-04-03 13:23:32 +00:00
---
# Functions for Working with URLs {#functions-for-working-with-urls}
2021-05-27 19:44:11 +00:00
All these functions do not follow the RFC. They are maximally simplified for improved performance.
2020-03-20 10:10:48 +00:00
## Functions that Extract Parts of a URL {#functions-that-extract-parts-of-a-url}
2020-03-20 10:10:48 +00:00
If the relevant part isnt present in a URL, an empty string is returned.
2020-03-20 10:10:48 +00:00
### protocol {#protocol}
Extracts the protocol from a URL.
2020-03-20 10:10:48 +00:00
Examples of typical returned values: http, https, ftp, mailto, tel, magnet…
2020-03-20 10:10:48 +00:00
### domain {#domain}
Extracts the hostname from a URL.
2020-03-20 10:10:48 +00:00
``` sql
domain(url)
```
**Arguments**
- `url` — URL. Type: [String](../../sql-reference/data-types/string.md).
The URL can be specified with or without a scheme. Examples:
2020-03-20 10:10:48 +00:00
``` text
svn+ssh://some.svn-hosting.com:80/repo/trunk
some.svn-hosting.com:80/repo/trunk
https://yandex.com/time/
```
For these examples, the `domain` function returns the following results:
2020-03-20 10:10:48 +00:00
``` text
some.svn-hosting.com
some.svn-hosting.com
yandex.com
```
**Returned values**
- Host name. If ClickHouse can parse the input string as a URL.
- Empty string. If ClickHouse cant parse the input string as a URL.
Type: `String`.
**Example**
2020-03-20 10:10:48 +00:00
``` sql
SELECT domain('svn+ssh://some.svn-hosting.com:80/repo/trunk');
```
2020-03-20 10:10:48 +00:00
``` text
┌─domain('svn+ssh://some.svn-hosting.com:80/repo/trunk')─┐
│ some.svn-hosting.com │
└────────────────────────────────────────────────────────┘
```
2020-03-20 10:10:48 +00:00
### domainWithoutWWW {#domainwithoutwww}
2020-03-20 10:10:48 +00:00
Returns the domain and removes no more than one www. from the beginning of it, if present.
2020-03-20 10:10:48 +00:00
### topLevelDomain {#topleveldomain}
Extracts the the top-level domain from a URL.
2020-03-20 10:10:48 +00:00
``` sql
topLevelDomain(url)
```
**Arguments**
- `url` — URL. Type: [String](../../sql-reference/data-types/string.md).
The URL can be specified with or without a scheme. Examples:
2020-03-20 10:10:48 +00:00
``` text
svn+ssh://some.svn-hosting.com:80/repo/trunk
some.svn-hosting.com:80/repo/trunk
https://yandex.com/time/
```
**Returned values**
- Domain name. If ClickHouse can parse the input string as a URL.
- Empty string. If ClickHouse cannot parse the input string as a URL.
Type: `String`.
**Example**
2020-03-20 10:10:48 +00:00
``` sql
SELECT topLevelDomain('svn+ssh://www.some.svn-hosting.com:80/repo/trunk');
```
2020-03-20 10:10:48 +00:00
``` text
┌─topLevelDomain('svn+ssh://www.some.svn-hosting.com:80/repo/trunk')─┐
│ com │
└────────────────────────────────────────────────────────────────────┘
```
2020-03-20 10:10:48 +00:00
### firstSignificantSubdomain {#firstsignificantsubdomain}
Returns the “first significant subdomain”. This is a non-standard concept specific to Yandex.Metrica. The first significant subdomain is a second-level domain if it is com, net, org, or co. Otherwise, it is a third-level domain. For example, `firstSignificantSubdomain (https://news.yandex.ru/) = yandex, firstSignificantSubdomain (https://news.yandex.com.tr/) = yandex`. The list of “insignificant” second-level domains and other implementation details may change in the future.
2020-03-20 10:10:48 +00:00
### cutToFirstSignificantSubdomain {#cuttofirstsignificantsubdomain}
2020-03-20 10:10:48 +00:00
Returns the part of the domain that includes top-level subdomains up to the “first significant subdomain” (see the explanation above).
For example:
- `cutToFirstSignificantSubdomain('https://news.yandex.com.tr/') = 'yandex.com.tr'`.
- `cutToFirstSignificantSubdomain('www.tr') = 'tr'`.
- `cutToFirstSignificantSubdomain('tr') = ''`.
### cutToFirstSignificantSubdomainWithWWW {#cuttofirstsignificantsubdomainwithwww}
Returns the part of the domain that includes top-level subdomains up to the “first significant subdomain”, without stripping "www".
For example:
- `cutToFirstSignificantSubdomain('https://news.yandex.com.tr/') = 'yandex.com.tr'`.
- `cutToFirstSignificantSubdomain('www.tr') = 'www.tr'`.
- `cutToFirstSignificantSubdomain('tr') = ''`.
### cutToFirstSignificantSubdomainCustom {#cuttofirstsignificantsubdomaincustom}
Returns the part of the domain that includes top-level subdomains up to the first significant subdomain. Accepts custom [TLD list](https://en.wikipedia.org/wiki/List_of_Internet_top-level_domains) name.
Can be useful if you need fresh TLD list or you have custom.
Configuration example:
```xml
<!-- <top_level_domains_path>/var/lib/clickhouse/top_level_domains/</top_level_domains_path> -->
<top_level_domains_lists>
<!-- https://publicsuffix.org/list/public_suffix_list.dat -->
<public_suffix_list>public_suffix_list.dat</public_suffix_list>
<!-- NOTE: path is under top_level_domains_path -->
</top_level_domains_lists>
```
**Syntax**
``` sql
cutToFirstSignificantSubdomain(URL, TLD)
```
**Parameters**
- `URL` — URL. [String](../../sql-reference/data-types/string.md).
- `TLD` — Custom TLD list name. [String](../../sql-reference/data-types/string.md).
**Returned value**
- Part of the domain that includes top-level subdomains up to the first significant subdomain.
Type: [String](../../sql-reference/data-types/string.md).
**Example**
Query:
```sql
SELECT cutToFirstSignificantSubdomainCustom('bar.foo.there-is-no-such-domain', 'public_suffix_list');
```
Result:
```text
┌─cutToFirstSignificantSubdomainCustom('bar.foo.there-is-no-such-domain', 'public_suffix_list')─┐
│ foo.there-is-no-such-domain │
└───────────────────────────────────────────────────────────────────────────────────────────────┘
```
**See Also**
- [firstSignificantSubdomain](#firstsignificantsubdomain).
### cutToFirstSignificantSubdomainCustomWithWWW {#cuttofirstsignificantsubdomaincustomwithwww}
Returns the part of the domain that includes top-level subdomains up to the first significant subdomain without stripping `www`. Accepts custom TLD list name.
Can be useful if you need fresh TLD list or you have custom.
Configuration example:
```xml
<!-- <top_level_domains_path>/var/lib/clickhouse/top_level_domains/</top_level_domains_path> -->
<top_level_domains_lists>
<!-- https://publicsuffix.org/list/public_suffix_list.dat -->
<public_suffix_list>public_suffix_list.dat</public_suffix_list>
<!-- NOTE: path is under top_level_domains_path -->
</top_level_domains_lists>
```
**Syntax**
```sql
cutToFirstSignificantSubdomainCustomWithWWW(URL, TLD)
```
**Parameters**
- `URL` — URL. [String](../../sql-reference/data-types/string.md).
- `TLD` — Custom TLD list name. [String](../../sql-reference/data-types/string.md).
**Returned value**
- Part of the domain that includes top-level subdomains up to the first significant subdomain without stripping `www`.
Type: [String](../../sql-reference/data-types/string.md).
**Example**
Query:
```sql
SELECT cutToFirstSignificantSubdomainCustomWithWWW('www.foo', 'public_suffix_list');
```
Result:
```text
┌─cutToFirstSignificantSubdomainCustomWithWWW('www.foo', 'public_suffix_list')─┐
│ www.foo │
└──────────────────────────────────────────────────────────────────────────────┘
```
**See Also**
- [firstSignificantSubdomain](#firstsignificantsubdomain).
### firstSignificantSubdomainCustom {#firstsignificantsubdomaincustom}
Returns the first significant subdomain. Accepts customs TLD list name.
Can be useful if you need fresh TLD list or you have custom.
Configuration example:
```xml
<!-- <top_level_domains_path>/var/lib/clickhouse/top_level_domains/</top_level_domains_path> -->
<top_level_domains_lists>
<!-- https://publicsuffix.org/list/public_suffix_list.dat -->
<public_suffix_list>public_suffix_list.dat</public_suffix_list>
<!-- NOTE: path is under top_level_domains_path -->
</top_level_domains_lists>
```
**Syntax**
```sql
firstSignificantSubdomainCustom(URL, TLD)
```
**Parameters**
- `URL` — URL. [String](../../sql-reference/data-types/string.md).
- `TLD` — Custom TLD list name. [String](../../sql-reference/data-types/string.md).
**Returned value**
- First significant subdomain.
Type: [String](../../sql-reference/data-types/string.md).
**Example**
Query:
```sql
SELECT firstSignificantSubdomainCustom('bar.foo.there-is-no-such-domain', 'public_suffix_list');
```
Result:
2021-07-29 15:20:55 +00:00
```text
┌─firstSignificantSubdomainCustom('bar.foo.there-is-no-such-domain', 'public_suffix_list')─┐
│ foo │
└──────────────────────────────────────────────────────────────────────────────────────────┘
```
**See Also**
- [firstSignificantSubdomain](#firstsignificantsubdomain).
2020-10-13 17:23:29 +00:00
### port(URL\[, default_port = 0\]) {#port}
Returns the port or `default_port` if there is no port in the URL (or in case of validation error).
2020-03-20 10:10:48 +00:00
### path {#path}
Returns the path. Example: `/top/news.html` The path does not include the query string.
2020-03-20 10:10:48 +00:00
### pathFull {#pathfull}
2020-10-13 17:23:29 +00:00
The same as above, but including query string and fragment. Example: /top/news.html?page=2#comments
2020-03-20 10:10:48 +00:00
### queryString {#querystring}
2020-10-13 17:23:29 +00:00
Returns the query string. Example: page=1&lr=213. query-string does not include the initial question mark, as well as # and everything after #.
2020-03-20 10:10:48 +00:00
### fragment {#fragment}
Returns the fragment identifier. fragment does not include the initial hash symbol.
2020-03-20 10:10:48 +00:00
### queryStringAndFragment {#querystringandfragment}
2020-10-13 17:23:29 +00:00
Returns the query string and fragment identifier. Example: page=1#29390.
2020-03-20 10:10:48 +00:00
### extractURLParameter(URL, name) {#extracturlparameterurl-name}
2020-03-20 10:10:48 +00:00
Returns the value of the name parameter in the URL, if present. Otherwise, an empty string. If there are many parameters with this name, it returns the first occurrence. This function works under the assumption that the parameter name is encoded in the URL exactly the same way as in the passed argument.
2020-03-20 10:10:48 +00:00
### extractURLParameters(URL) {#extracturlparametersurl}
Returns an array of name=value strings corresponding to the URL parameters. The values are not decoded in any way.
2020-03-20 10:10:48 +00:00
### extractURLParameterNames(URL) {#extracturlparameternamesurl}
Returns an array of name strings corresponding to the names of URL parameters. The values are not decoded in any way.
2020-03-20 10:10:48 +00:00
### URLHierarchy(URL) {#urlhierarchyurl}
Returns an array containing the URL, truncated at the end by the symbols /,? in the path and query-string. Consecutive separator characters are counted as one. The cut is made in the position after all the consecutive separator characters.
2020-03-20 10:10:48 +00:00
### URLPathHierarchy(URL) {#urlpathhierarchyurl}
The same as above, but without the protocol and host in the result. The / element (root) is not included. Example: the function is used to implement tree reports the URL in Yandex. Metric.
2020-03-20 10:10:48 +00:00
``` text
URLPathHierarchy('https://example.com/browse/CONV-6788') =
[
'/browse/',
'/browse/CONV-6788'
]
```
2020-03-20 10:10:48 +00:00
### decodeURLComponent(URL) {#decodeurlcomponenturl}
Returns the decoded URL.
Example:
2020-03-20 10:10:48 +00:00
``` sql
SELECT decodeURLComponent('http://127.0.0.1:8123/?query=SELECT%201%3B') AS DecodedURL;
```
2020-03-20 10:10:48 +00:00
``` text
┌─DecodedURL─────────────────────────────┐
│ http://127.0.0.1:8123/?query=SELECT 1; │
└────────────────────────────────────────┘
```
### netloc {#netloc}
Extracts network locality (`username:password@host:port`) from a URL.
**Syntax**
2020-07-11 11:05:49 +00:00
``` sql
netloc(URL)
```
**Arguments**
- `url` — URL. [String](../../sql-reference/data-types/string.md).
**Returned value**
2020-07-11 11:05:49 +00:00
- `username:password@host:port`.
Type: `String`.
**Example**
Query:
``` sql
SELECT netloc('http://paul@www.example.com:80/');
```
Result:
``` text
┌─netloc('http://paul@www.example.com:80/')─┐
│ paul@www.example.com:80 │
└───────────────────────────────────────────┘
```
## Functions that Remove Part of a URL {#functions-that-remove-part-of-a-url}
2021-05-27 19:44:11 +00:00
If the URL does not have anything similar, the URL remains unchanged.
2020-03-20 10:10:48 +00:00
### cutWWW {#cutwww}
2020-03-20 10:10:48 +00:00
Removes no more than one www. from the beginning of the URLs domain, if present.
2020-03-20 10:10:48 +00:00
### cutQueryString {#cutquerystring}
Removes query string. The question mark is also removed.
2020-03-20 10:10:48 +00:00
### cutFragment {#cutfragment}
Removes the fragment identifier. The number sign is also removed.
2020-03-20 10:10:48 +00:00
### cutQueryStringAndFragment {#cutquerystringandfragment}
Removes the query string and fragment identifier. The question mark and number sign are also removed.
2020-03-20 10:10:48 +00:00
### cutURLParameter(URL, name) {#cuturlparameterurl-name}
2020-03-20 10:10:48 +00:00
Removes the name URL parameter, if present. This function works under the assumption that the parameter name is encoded in the URL exactly the same way as in the passed argument.