[jira] [Updated] (HBASE-12938) Upgrade HTrace to a recent supportable incubating version

2015-03-18 Thread Andrew Purtell (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-12938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Purtell updated HBASE-12938:
---
Fix Version/s: (was: 0.98.12)
   0.98.13

 Upgrade HTrace to a recent supportable incubating version
 -

 Key: HBASE-12938
 URL: https://issues.apache.org/jira/browse/HBASE-12938
 Project: HBase
  Issue Type: Bug
Reporter: Andrew Purtell
 Fix For: 0.98.13


 In 0.98 we have an old htrace (still using the org.cloudera.htrace package) 
 and since the introduction of htrace code, htrace itself first moved to 
 org.htrace, then became an incubating project. I filed this as a bug because 
 the HTrace version we reference in 0.98 is of little to no use going forward. 
 Unfortunately we must make a disruptive change, although it looks to be 
 mostly fixing up imports, we expose no HTrace classes to HBase configuration, 
 and where we extend HTrace classes in our code, those HBase classes are in 
 hbase-server and not tagged for public consumption.   



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-12938) Upgrade HTrace to a recent supportable incubating version

2015-03-02 Thread Andrew Purtell (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-12938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Purtell updated HBASE-12938:
---
Fix Version/s: (was: 0.98.11)
   0.98.12
 Assignee: (was: Andrew Purtell)

Didn't get time for this. Moving out to 0.98.12 and unassigning

 Upgrade HTrace to a recent supportable incubating version
 -

 Key: HBASE-12938
 URL: https://issues.apache.org/jira/browse/HBASE-12938
 Project: HBase
  Issue Type: Bug
Reporter: Andrew Purtell
 Fix For: 0.98.12


 In 0.98 we have an old htrace (still using the org.cloudera.htrace package) 
 and since the introduction of htrace code, htrace itself first moved to 
 org.htrace, then became an incubating project. I filed this as a bug because 
 the HTrace version we reference in 0.98 is of little to no use going forward. 
 Unfortunately we must make a disruptive change, although it looks to be 
 mostly fixing up imports, we expose no HTrace classes to HBase configuration, 
 and where we extend HTrace classes in our code, those HBase classes are in 
 hbase-server and not tagged for public consumption.   



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-12938) Upgrade HTrace to a recent supportable incubating version

2015-01-28 Thread Andrew Purtell (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-12938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Purtell updated HBASE-12938:
---
Assignee: Andrew Purtell

Let me assign this to myself to tinker around with it ahead of the next 0.98 
release. 

 Upgrade HTrace to a recent supportable incubating version
 -

 Key: HBASE-12938
 URL: https://issues.apache.org/jira/browse/HBASE-12938
 Project: HBase
  Issue Type: Bug
Reporter: Andrew Purtell
Assignee: Andrew Purtell
 Fix For: 0.98.11


 In 0.98 we have an old htrace (still using the org.cloudera.htrace package) 
 and since the introduction of htrace code, htrace itself first moved to 
 org.htrace, then became an incubating project. I filed this as a bug because 
 the HTrace version we reference in 0.98 is of little to no use going forward. 
 Unfortunately we must make a disruptive change, although it looks to be 
 mostly fixing up imports, we expose no HTrace classes to HBase configuration, 
 and where we extend HTrace classes in our code, those HBase classes are in 
 hbase-server and not tagged for public consumption.   



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-12938) Upgrade HTrace to a recent supportable incubating version

2015-01-28 Thread Andrew Purtell (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-12938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Purtell updated HBASE-12938:
---
Description: In 0.98 we have an old htrace (still using the 
org.cloudera.htrace package) and since the introduction of htrace code, htrace 
itself first moved to org.htrace, then became an incubating project. I filed 
this as a bug because the HTrace version we reference in 0.98 is of little to 
no use going forward. Unfortunately we must make a disruptive change, although 
it looks to be mostly fixing up imports, we expose no HTrace classes to HBase 
configuration, and where we extend HTrace classes in our code, those HBase 
classes are in hbase-server and not tagged for public consumption. (was: I 
filed this as a bug because in 0.98 we have an old htrace (still using the 
org.cloudera.htrace package) and since the introduction of htrace code, htrace 
itself first moved to org.htrace, then became an incubating project. The 
version we reference in 0.98 is of little to no use going forward. 
Unfortunately we must make a disruptive change, although it looks to be mostly 
fixing up imports, we expose no HTrace classes to HBase configuration, and 
where we extend HTrace classes in our code, those HBase classes are in 
hbase-server and not tagged for public consumption.   )

 Upgrade HTrace to a recent supportable incubating version
 -

 Key: HBASE-12938
 URL: https://issues.apache.org/jira/browse/HBASE-12938
 Project: HBase
  Issue Type: Bug
Reporter: Andrew Purtell
 Fix For: 0.98.11


 In 0.98 we have an old htrace (still using the org.cloudera.htrace package) 
 and since the introduction of htrace code, htrace itself first moved to 
 org.htrace, then became an incubating project. I filed this as a bug because 
 the HTrace version we reference in 0.98 is of little to no use going forward. 
 Unfortunately we must make a disruptive change, although it looks to be 
 mostly fixing up imports, we expose no HTrace classes to HBase configuration, 
 and where we extend HTrace classes in our code, those HBase classes are in 
 hbase-server and not tagged for public consumption.   



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)