[jira] [Commented] (HBASE-18388) Fix description on region page, explaining what a region name is made of

2020-10-08 Thread Viraj Jasani (Jira)


[ 
https://issues.apache.org/jira/browse/HBASE-18388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17210175#comment-17210175
 ] 

Viraj Jasani commented on HBASE-18388:
--

[~mirkojotic] added you also as a contributor. Going forward, you can assign 
any unassigned Jira to you. Moreover, once assigned, you can raise a github PR 
with title covering Jira so that the PR will get linked here automatically. You 
can get more details in "Github" section under 
[https://hbase.apache.org/book.html#developing].

> Fix description on region page, explaining what a region name is made of
> 
>
> Key: HBASE-18388
> URL: https://issues.apache.org/jira/browse/HBASE-18388
> Project: HBase
>  Issue Type: Improvement
>  Components: master, regionserver, UI
>Affects Versions: 1.3.1, 2.0.0-alpha-1
>Reporter: Lars George
>Assignee: Sourabh Dhanotia
>Priority: Minor
>  Labels: beginner
>
> In the {{RegionListTmpl.jamon}} we have this:
> {code}
> Region names are made of the containing table's name, a comma,
> the start key, a comma, and a randomly generated region id.  To 
> illustrate,
> the region named
> domains,apache.org,5464829424211263407 is party to the table
> domains, has an id of 5464829424211263407 and the first 
> key
> in the region is apache.org.The hbase:meta 'table' 
> is an internal
> system table (or a 'catalog' table in db-speak).
> The hbase:meta table keeps a list of all regions in the system. The empty 
> key is used to denote
> table start and table end.  A region with an empty start key is the first 
> region in a table.
> If a region has both an empty start key and an empty end key, it's the 
> only region in the
> table. See http://hbase.org";>HBase Home for further 
> explication.
> {code}
> This is wrong and worded oddly. What needs to be fixed facts wise is:
> - Region names contain (separated by commas) the full table name (including 
> the namespace), the start key, the time the region was created, and finally a 
> dot with an MD5 hash of everything before the dot. For example: 
> {{test,,1499410125885.1544f69aeaf787755caa11d3567a9621.}}
> - The trailing dot is to distinguish legacy region names (like those used by 
> the {{hbase:meta}} table)
> - The MD5 hash is used as the directory name within the HBase storage 
> directories
> - The names for the meta table use a Jenkins hash instead, also leaving out 
> the trailing dot, for example {{hbase:meta,,1.1588230740}}. The time is 
> always set to {{1}}.
> - The start key is printed in safe characters, escaping unprintable characters
> - The link to the HBase home page to explain more is useless and should be 
> removed.
> - Also, for region replicas, the replica ID is inserted into the name, like 
> so {{replicatable,,1486289678486_0001.3e8b7655299b21b3038ff8d39062467f.}}, 
> see the {{_0001}} part.
> As for the wording, I would just make this all flow a little better, that "is 
> party of" sounds weird to me (IMHO).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (HBASE-18388) Fix description on region page, explaining what a region name is made of

2020-10-08 Thread Viraj Jasani (Jira)


[ 
https://issues.apache.org/jira/browse/HBASE-18388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17210173#comment-17210173
 ] 

Viraj Jasani commented on HBASE-18388:
--

Done [~sourabhdhanotia], added you to the contributor's list so that you can 
assign any unassigned Jira to you.

Thanks

> Fix description on region page, explaining what a region name is made of
> 
>
> Key: HBASE-18388
> URL: https://issues.apache.org/jira/browse/HBASE-18388
> Project: HBase
>  Issue Type: Improvement
>  Components: master, regionserver, UI
>Affects Versions: 1.3.1, 2.0.0-alpha-1
>Reporter: Lars George
>Assignee: Sourabh Dhanotia
>Priority: Minor
>  Labels: beginner
>
> In the {{RegionListTmpl.jamon}} we have this:
> {code}
> Region names are made of the containing table's name, a comma,
> the start key, a comma, and a randomly generated region id.  To 
> illustrate,
> the region named
> domains,apache.org,5464829424211263407 is party to the table
> domains, has an id of 5464829424211263407 and the first 
> key
> in the region is apache.org.The hbase:meta 'table' 
> is an internal
> system table (or a 'catalog' table in db-speak).
> The hbase:meta table keeps a list of all regions in the system. The empty 
> key is used to denote
> table start and table end.  A region with an empty start key is the first 
> region in a table.
> If a region has both an empty start key and an empty end key, it's the 
> only region in the
> table. See http://hbase.org";>HBase Home for further 
> explication.
> {code}
> This is wrong and worded oddly. What needs to be fixed facts wise is:
> - Region names contain (separated by commas) the full table name (including 
> the namespace), the start key, the time the region was created, and finally a 
> dot with an MD5 hash of everything before the dot. For example: 
> {{test,,1499410125885.1544f69aeaf787755caa11d3567a9621.}}
> - The trailing dot is to distinguish legacy region names (like those used by 
> the {{hbase:meta}} table)
> - The MD5 hash is used as the directory name within the HBase storage 
> directories
> - The names for the meta table use a Jenkins hash instead, also leaving out 
> the trailing dot, for example {{hbase:meta,,1.1588230740}}. The time is 
> always set to {{1}}.
> - The start key is printed in safe characters, escaping unprintable characters
> - The link to the HBase home page to explain more is useless and should be 
> removed.
> - Also, for region replicas, the replica ID is inserted into the name, like 
> so {{replicatable,,1486289678486_0001.3e8b7655299b21b3038ff8d39062467f.}}, 
> see the {{_0001}} part.
> As for the wording, I would just make this all flow a little better, that "is 
> party of" sounds weird to me (IMHO).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (HBASE-18388) Fix description on region page, explaining what a region name is made of

2020-10-08 Thread Sourabh Dhanotia (Jira)


[ 
https://issues.apache.org/jira/browse/HBASE-18388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17210171#comment-17210171
 ] 

Sourabh Dhanotia commented on HBASE-18388:
--

[~vjasani] I would like to take this up. Could you please assign it to me

> Fix description on region page, explaining what a region name is made of
> 
>
> Key: HBASE-18388
> URL: https://issues.apache.org/jira/browse/HBASE-18388
> Project: HBase
>  Issue Type: Improvement
>  Components: master, regionserver, UI
>Affects Versions: 1.3.1, 2.0.0-alpha-1
>Reporter: Lars George
>Priority: Minor
>  Labels: beginner
>
> In the {{RegionListTmpl.jamon}} we have this:
> {code}
> Region names are made of the containing table's name, a comma,
> the start key, a comma, and a randomly generated region id.  To 
> illustrate,
> the region named
> domains,apache.org,5464829424211263407 is party to the table
> domains, has an id of 5464829424211263407 and the first 
> key
> in the region is apache.org.The hbase:meta 'table' 
> is an internal
> system table (or a 'catalog' table in db-speak).
> The hbase:meta table keeps a list of all regions in the system. The empty 
> key is used to denote
> table start and table end.  A region with an empty start key is the first 
> region in a table.
> If a region has both an empty start key and an empty end key, it's the 
> only region in the
> table. See http://hbase.org";>HBase Home for further 
> explication.
> {code}
> This is wrong and worded oddly. What needs to be fixed facts wise is:
> - Region names contain (separated by commas) the full table name (including 
> the namespace), the start key, the time the region was created, and finally a 
> dot with an MD5 hash of everything before the dot. For example: 
> {{test,,1499410125885.1544f69aeaf787755caa11d3567a9621.}}
> - The trailing dot is to distinguish legacy region names (like those used by 
> the {{hbase:meta}} table)
> - The MD5 hash is used as the directory name within the HBase storage 
> directories
> - The names for the meta table use a Jenkins hash instead, also leaving out 
> the trailing dot, for example {{hbase:meta,,1.1588230740}}. The time is 
> always set to {{1}}.
> - The start key is printed in safe characters, escaping unprintable characters
> - The link to the HBase home page to explain more is useless and should be 
> removed.
> - Also, for region replicas, the replica ID is inserted into the name, like 
> so {{replicatable,,1486289678486_0001.3e8b7655299b21b3038ff8d39062467f.}}, 
> see the {{_0001}} part.
> As for the wording, I would just make this all flow a little better, that "is 
> party of" sounds weird to me (IMHO).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (HBASE-18388) Fix description on region page, explaining what a region name is made of

2020-01-29 Thread Mirko Jotic (Jira)


[ 
https://issues.apache.org/jira/browse/HBASE-18388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17026025#comment-17026025
 ] 

Mirko Jotic commented on HBASE-18388:
-

[~liyu] if this is still relevant I'd like to submit a patch. Is there 
something I need to do before I'm allowed to submit a patch? Executing 
submit-patch.py is giving me 403 from Jira API.

> Fix description on region page, explaining what a region name is made of
> 
>
> Key: HBASE-18388
> URL: https://issues.apache.org/jira/browse/HBASE-18388
> Project: HBase
>  Issue Type: Improvement
>  Components: master, regionserver, UI
>Affects Versions: 1.3.1, 2.0.0-alpha-1
>Reporter: Lars George
>Priority: Minor
>  Labels: beginner
>
> In the {{RegionListTmpl.jamon}} we have this:
> {code}
> Region names are made of the containing table's name, a comma,
> the start key, a comma, and a randomly generated region id.  To 
> illustrate,
> the region named
> domains,apache.org,5464829424211263407 is party to the table
> domains, has an id of 5464829424211263407 and the first 
> key
> in the region is apache.org.The hbase:meta 'table' 
> is an internal
> system table (or a 'catalog' table in db-speak).
> The hbase:meta table keeps a list of all regions in the system. The empty 
> key is used to denote
> table start and table end.  A region with an empty start key is the first 
> region in a table.
> If a region has both an empty start key and an empty end key, it's the 
> only region in the
> table. See http://hbase.org";>HBase Home for further 
> explication.
> {code}
> This is wrong and worded oddly. What needs to be fixed facts wise is:
> - Region names contain (separated by commas) the full table name (including 
> the namespace), the start key, the time the region was created, and finally a 
> dot with an MD5 hash of everything before the dot. For example: 
> {{test,,1499410125885.1544f69aeaf787755caa11d3567a9621.}}
> - The trailing dot is to distinguish legacy region names (like those used by 
> the {{hbase:meta}} table)
> - The MD5 hash is used as the directory name within the HBase storage 
> directories
> - The names for the meta table use a Jenkins hash instead, also leaving out 
> the trailing dot, for example {{hbase:meta,,1.1588230740}}. The time is 
> always set to {{1}}.
> - The start key is printed in safe characters, escaping unprintable characters
> - The link to the HBase home page to explain more is useless and should be 
> removed.
> - Also, for region replicas, the replica ID is inserted into the name, like 
> so {{replicatable,,1486289678486_0001.3e8b7655299b21b3038ff8d39062467f.}}, 
> see the {{_0001}} part.
> As for the wording, I would just make this all flow a little better, that "is 
> party of" sounds weird to me (IMHO).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (HBASE-18388) Fix description on region page, explaining what a region name is made of

2019-09-06 Thread Sanjeet Nishad (Jira)


[ 
https://issues.apache.org/jira/browse/HBASE-18388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924078#comment-16924078
 ] 

Sanjeet Nishad commented on HBASE-18388:


Hi,

[~larsgeorge] are you working on this or should I share a patch for this?

> Fix description on region page, explaining what a region name is made of
> 
>
> Key: HBASE-18388
> URL: https://issues.apache.org/jira/browse/HBASE-18388
> Project: HBase
>  Issue Type: Improvement
>  Components: master, regionserver, UI
>Affects Versions: 1.3.1, 2.0.0-alpha-1
>Reporter: Lars George
>Priority: Minor
>  Labels: beginner
>
> In the {{RegionListTmpl.jamon}} we have this:
> {code}
> Region names are made of the containing table's name, a comma,
> the start key, a comma, and a randomly generated region id.  To 
> illustrate,
> the region named
> domains,apache.org,5464829424211263407 is party to the table
> domains, has an id of 5464829424211263407 and the first 
> key
> in the region is apache.org.The hbase:meta 'table' 
> is an internal
> system table (or a 'catalog' table in db-speak).
> The hbase:meta table keeps a list of all regions in the system. The empty 
> key is used to denote
> table start and table end.  A region with an empty start key is the first 
> region in a table.
> If a region has both an empty start key and an empty end key, it's the 
> only region in the
> table. See http://hbase.org";>HBase Home for further 
> explication.
> {code}
> This is wrong and worded oddly. What needs to be fixed facts wise is:
> - Region names contain (separated by commas) the full table name (including 
> the namespace), the start key, the time the region was created, and finally a 
> dot with an MD5 hash of everything before the dot. For example: 
> {{test,,1499410125885.1544f69aeaf787755caa11d3567a9621.}}
> - The trailing dot is to distinguish legacy region names (like those used by 
> the {{hbase:meta}} table)
> - The MD5 hash is used as the directory name within the HBase storage 
> directories
> - The names for the meta table use a Jenkins hash instead, also leaving out 
> the trailing dot, for example {{hbase:meta,,1.1588230740}}. The time is 
> always set to {{1}}.
> - The start key is printed in safe characters, escaping unprintable characters
> - The link to the HBase home page to explain more is useless and should be 
> removed.
> - Also, for region replicas, the replica ID is inserted into the name, like 
> so {{replicatable,,1486289678486_0001.3e8b7655299b21b3038ff8d39062467f.}}, 
> see the {{_0001}} part.
> As for the wording, I would just make this all flow a little better, that "is 
> party of" sounds weird to me (IMHO).



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (HBASE-18388) Fix description on region page, explaining what a region name is made of

2017-07-16 Thread Yu Li (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-18388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16089247#comment-16089247
 ] 

Yu Li commented on HBASE-18388:
---

Nice catch and good suggestions. Mind uploading a patch? [~larsgeorge]

[~misty] FYI sir.

> Fix description on region page, explaining what a region name is made of
> 
>
> Key: HBASE-18388
> URL: https://issues.apache.org/jira/browse/HBASE-18388
> Project: HBase
>  Issue Type: Improvement
>  Components: master, regionserver, UI
>Affects Versions: 1.3.1, 2.0.0-alpha-1
>Reporter: Lars George
>Priority: Minor
>  Labels: beginner
>
> In the {{RegionListTmpl.jamon}} we have this:
> {code}
> Region names are made of the containing table's name, a comma,
> the start key, a comma, and a randomly generated region id.  To 
> illustrate,
> the region named
> domains,apache.org,5464829424211263407 is party to the table
> domains, has an id of 5464829424211263407 and the first 
> key
> in the region is apache.org.The hbase:meta 'table' 
> is an internal
> system table (or a 'catalog' table in db-speak).
> The hbase:meta table keeps a list of all regions in the system. The empty 
> key is used to denote
> table start and table end.  A region with an empty start key is the first 
> region in a table.
> If a region has both an empty start key and an empty end key, it's the 
> only region in the
> table. See http://hbase.org";>HBase Home for further 
> explication.
> {code}
> This is wrong and worded oddly. What needs to be fixed facts wise is:
> - Region names contain (separated by commas) the full table name (including 
> the namespace), the start key, the time the region was created, and finally a 
> dot with an MD5 hash of everything before the dot. For example: 
> {{test,,1499410125885.1544f69aeaf787755caa11d3567a9621.}}
> - The trailing dot is to distinguish legacy region names (like those used by 
> the {{hbase:meta}} table)
> - The MD5 hash is used as the directory name within the HBase storage 
> directories
> - The names for the meta table use a Jenkins hash instead, also leaving out 
> the trailing dot, for example {{hbase:meta,,1.1588230740}}. The time is 
> always set to {{1}}.
> - The start key is printed in safe characters, escaping unprintable characters
> - The link to the HBase home page to explain more is useless and should be 
> removed.
> - Also, for region replicas, the replica ID is inserted into the name, like 
> so {{replicatable,,1486289678486_0001.3e8b7655299b21b3038ff8d39062467f.}}, 
> see the {{_0001}} part.
> As for the wording, I would just make this all flow a little better, that "is 
> party of" sounds weird to me (IMHO).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)